biztrac. BETA
COMPANY REGISTER PROFILE
930720089 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

UKE AS

Org. no. 930720089 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 82,000
Operating profit NOK 57,000
Equity NOK 165,000
Incorporated 2022
Share capital NOK 30,000

UKE AS is registered as a limited company in Oslo, Oslo with organisation number 930720089. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 82,000 in revenue and NOK 57,000 in operating profit.

Key figures · 2025

Revenue
NOK 82,000
▲ +34 %
Operating profit
NOK 57,000
▲ +48 %
Equity
NOK 165,000
▲ +36 %
Est. value
NOK 231,000

Financial health · 2025

Liquidity
4.54
Very good
Current assets ÷ current liabilities
Profitability
31.9%
Very good
Return on total assets
Solidity
82.6%
Very good
Equity as a share of total capital

Who owns UKE AS?

UKE AS
NOK 82,000 rev. · NOK 57,000 profit

UKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UKE AS own?

UKE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about UKE AS

Who owns UKE AS?

Knut Einar Hagen is the largest registered owner, with 100.0%.

What is the revenue of UKE AS?

UKE AS had revenue of NOK 82,000 in 2025.

Who is the general manager of UKE AS?

Knut Einar Hagen is registered as general manager of UKE AS.

Where is UKE AS based?

UKE AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.