BIZTRAC BETA
Other captive investment companies

FREDRIKSEN LEVIN AS

Org. no. 919560487 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK −309,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−309k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

FREDRIKSEN LEVIN AS is registered as a limited company in Oslo, Oslo with organisation number 919560487. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Deltagelse i andre virksomheter, investering i andre selskaper, investeringer i andre verdipapirer investering i eiendom og annet som står i sammenheng med dette.”.

Key figures · 2024

Operating profit
NOK −24,000
Equity
NOK −309,000

Financial health · 2024

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-52.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FREDRIKSEN LEVIN AS?

RIOT & SONS AS
FREDRIKSEN LEVIN AS
· NOK −24,000 profit

FREDRIKSEN LEVIN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FREDRIKSEN LEVIN AS own?

FREDRIKSEN LEVIN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FREDRIKSEN LEVIN AS

Who owns FREDRIKSEN LEVIN AS?

RIOT & SONS AS is the largest registered owner, with 50.0%.

Who is the general manager of FREDRIKSEN LEVIN AS?

Geir Fredriksen is registered as general manager of FREDRIKSEN LEVIN AS.

Where is FREDRIKSEN LEVIN AS based?

FREDRIKSEN LEVIN 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.