BIZTRAC BETA
Rental and operating of own or leased real estate

FJELLHAMAR BRUK AS

Org. no. 917653127 Limited company (AS) Lørenskog Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.4m
Equity NOK 412.4m
Incorporated 2016
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

FJELLHAMAR BRUK AS is registered as a limited company in Lørenskog, Akershus with organisation number 917653127. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.4m
Equity
NOK 412.4m
Est. value
NOK 424.9m

Financial health · 2024

Liquidity
5.68
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.4%
Very good
Equity as a share of total capital

Who owns FJELLHAMAR BRUK AS?

METEVA AS
FJELLHAMAR BRUK AS
NOK 0 rev. · NOK −1.4m profit

FJELLHAMAR BRUK AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about FJELLHAMAR BRUK AS

Who owns FJELLHAMAR BRUK AS?

METEVA AS is the largest registered owner, with 14.8%.

What is the revenue of FJELLHAMAR BRUK AS?

FJELLHAMAR BRUK AS had revenue of NOK 0 in 2024.

Who is the general manager of FJELLHAMAR BRUK AS?

Stig Hvinden is registered as general manager of FJELLHAMAR BRUK AS.

Where is FJELLHAMAR BRUK AS based?

FJELLHAMAR BRUK AS has its business address in Fjellhamar.

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.