BIZTRAC BETA
Development of building projects

MANNFJELL EIENDOM AS

Org. no. 931441493 Limited company (AS) Meråker Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 14,000
Equity NOK −540,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−540k kr).

MANNFJELL EIENDOM AS is registered as a limited company in Meråker, Trøndelag with organisation number 931441493. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie aksjer i andre selskaper. Selskapet kan også kjøpe og selge eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 14,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 14,000
Equity
NOK −540,000
Est. value
NOK 94,000

Financial health · 2024

Liquidity
2.96
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.2%
Weak
Equity as a share of total capital

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

Who owns MANNFJELL EIENDOM AS?

ENERGILAFT AS
MANNFJELL EIENDOM AS
NOK 0 rev. · NOK 14,000 profit

MANNFJELL EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MANNFJELL EIENDOM AS own?

MANNFJELL EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MANNFJELL EIENDOM AS

Who owns MANNFJELL EIENDOM AS?

ENERGILAFT AS is the largest registered owner, with 83.3%.

What is the revenue of MANNFJELL EIENDOM AS?

MANNFJELL EIENDOM AS had revenue of NOK 0 in 2024.

Where is MANNFJELL EIENDOM AS based?

MANNFJELL EIENDOM AS has its business address in Meråker.

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.