BIZTRAC BETA
Uoppgitt

FSO INVEST AS

Org. no. 913157737 Limited company (AS) Lillehammer Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK −8,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−8k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

FSO INVEST AS is registered as a limited company in Lillehammer, Innlandet with organisation number 913157737. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, samt på andre måter gjøre seg interessert og investere i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK −8,000

Financial health · 2025

Liquidity
0.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-176.3%
Weak
Equity as a share of total capital

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

Who owns FSO INVEST AS?

FREDRIK STRAND OSEBERG
FSO INVEST AS
NOK 0 rev. · NOK −5,000 profit

FSO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FSO INVEST AS

Who owns FSO INVEST AS?

FREDRIK STRAND OSEBERG is the largest registered owner, with 100.0%.

What is the revenue of FSO INVEST AS?

FSO INVEST AS had revenue of NOK 0 in 2025.

Where is FSO INVEST AS based?

FSO INVEST AS has its business address in Lillehammer.

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.