biztrac. BETA
COMPANY REGISTER PROFILE
892914222 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

FISKARSKOGEN EIENDOM AS

Org. no. 892914222 Limited company (AS) Bjørnafjorden Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −43,000
Equity NOK −361,000
Incorporated 2008
Share capital NOK 100,000

Signals

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

FISKARSKOGEN EIENDOM AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 892914222. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i eiendommer og drift, samt det som naturlig hører til dette, samt å eie aksjer og andeler i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −43,000
▼ −6 %
Equity
NOK −361,000
▼ −13 %

Financial health · 2025

Liquidity
19.07
Very good
Current assets ÷ current liabilities
Profitability
-0.6%
Not satisfactory
Return on total assets
Solidity
-4.1%
Weak
Equity as a share of total capital

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

Who owns FISKARSKOGEN EIENDOM AS?

FISKARSKOGEN EIENDOM AS
· NOK −43,000 profit

FISKARSKOGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FISKARSKOGEN EIENDOM AS

Who owns FISKARSKOGEN EIENDOM AS?

LYSEPARKEN VEST HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of FISKARSKOGEN EIENDOM AS?

Fredrik Storum is registered as general manager of FISKARSKOGEN EIENDOM AS.

Where is FISKARSKOGEN EIENDOM AS based?

FISKARSKOGEN EIENDOM AS has its business address in Os.

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.