BIZTRAC BETA
Other real estate activities on a fee or contract basis

MOA EIENDOM AS

Org. no. 997128966 Limited company (AS) Orkland Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 632,000
Equity NOK −394,000
Incorporated 2011
Share capital NOK 400,000

Signals

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

MOA EIENDOM AS is registered as a limited company in Orkland, Trøndelag with organisation number 997128966. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2011. Registered share capital is NOK 400,000, divided into 200 shares. The company's stated purpose is: “Investering i eiendom og anleggsutstyr med utleie av eiendeler, samt annen utleievirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 632,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 632,000
Equity
NOK −394,000
Est. value
NOK 4.3m

Financial health · 2024

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

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

Who owns MOA EIENDOM AS?

TORGEIR SLETVOLD
MOA EIENDOM AS
NOK 1.5m rev. · NOK 632,000 profit

MOA EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOA EIENDOM AS

Who owns MOA EIENDOM AS?

TORGEIR SLETVOLD is the largest registered owner, with 33.5%.

What is the revenue of MOA EIENDOM AS?

MOA EIENDOM AS had revenue of NOK 1.5m in 2024.

Who is the general manager of MOA EIENDOM AS?

Torgeir Sletvold is registered as general manager of MOA EIENDOM AS.

Where is MOA EIENDOM AS based?

MOA EIENDOM AS has its business address in Orkanger.

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.