BIZTRAC BETA
Other captive investment companies

UNITEL AS

Org. no. 989029681 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −226,000
Equity NOK 229.6m
Incorporated 2005
Share capital NOK 328,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−226k kr).

UNITEL AS is registered as a limited company in Oslo, Oslo with organisation number 989029681. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 328,000, divided into 1 shares. The company's stated purpose is: “Forretningsdrift av enhver art, herunder kjøp og salg av olje og oljeprodukter, aksjer, obligasjoner, skip, fast eiendom, interessentinnskudd av hvilken som helst type, ytelse av lån eller garanti for lån, samt enhver virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −226,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −226,000
Equity
NOK 229.6m
Est. value
NOK 684.9m

Financial health · 2024

Liquidity
5.76
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.5%
Very good
Equity as a share of total capital

Who owns UNITEL AS?

BJØRN ERLING KNAPPSKOG
UNITEL AS
NOK 0 rev. · NOK −226,000 profit

UNITEL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UNITEL AS own?

UNITEL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about UNITEL AS

Who owns UNITEL AS?

BJØRN ERLING KNAPPSKOG is the largest registered owner, with 100.0%.

What is the revenue of UNITEL AS?

UNITEL AS had revenue of NOK 0 in 2024.

Where is UNITEL AS based?

UNITEL 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 15.06.2026.

Report a problem

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