BIZTRAC BETA
Rental and operating of own or leased real estate

FJELLHEIMVEIEN 2 AS

Org. no. 997260368 Limited company (AS) Drammen Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 109,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

FJELLHEIMVEIEN 2 AS is registered as a limited company in Drammen, Buskerud with organisation number 997260368. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, drift og salg av fast eiendom og alt som står i forbindelse med dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 109,000
Est. value
NOK 99,000

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.4%
Good
Equity as a share of total capital

Who owns FJELLHEIMVEIEN 2 AS?

JADEFO HOLDING AS
FJELLHEIMVEIEN 2 AS
NOK 0 rev. · NOK −9,000 profit

FJELLHEIMVEIEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJELLHEIMVEIEN 2 AS

Who owns FJELLHEIMVEIEN 2 AS?

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

What is the revenue of FJELLHEIMVEIEN 2 AS?

FJELLHEIMVEIEN 2 AS had revenue of NOK 0 in 2025.

Who is the general manager of FJELLHEIMVEIEN 2 AS?

Jack Dean Fossum is registered as general manager of FJELLHEIMVEIEN 2 AS.

Where is FJELLHEIMVEIEN 2 AS based?

FJELLHEIMVEIEN 2 AS has its business address in Mjøndalen.

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.