biztrac. BETA
COMPANY REGISTER PROFILE
942910908 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

LEVANTEN AS

Org. no. 942910908 Limited company (AS) Bærum Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 125,000
Operating profit NOK −328,000
Equity NOK 15.0m
Incorporated 1987
Share capital NOK 568,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−328k kr).

LEVANTEN AS is registered as a limited company in Bærum, Akershus with organisation number 942910908. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1987. Registered share capital is NOK 568,000, divided into 5684 shares. The company's stated purpose is: “Shipping, handel, investeringer og annen nærings- virksomhet, samt hva herved står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 125,000 in revenue and NOK −328,000 in operating profit.

Key figures · 2025

Revenue
NOK 125,000
▲ +0 %
Operating profit
NOK −328,000
▼ −35 %
Equity
NOK 15.0m
▼ −3 %
Est. value
NOK 49.1m

Financial health · 2025

Liquidity
6.12
Very good
Current assets ÷ current liabilities
Profitability
35.4%
Very good
Return on total assets
Solidity
64.9%
Very good
Equity as a share of total capital

Who owns LEVANTEN AS?

LEVANTEN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LEVANTEN AS own?

LEVANTEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LEVANTEN AS

Who owns LEVANTEN AS?

Kristin Klevås Jahren is the largest registered owner, with 41.0%.

What is the revenue of LEVANTEN AS?

LEVANTEN AS had revenue of NOK 125,000 in 2025.

Where is LEVANTEN AS based?

LEVANTEN AS has its business address in Sandvika.

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.