BIZTRAC BETA
Rental and operating of own or leased real estate

3.M EIENDOM AS

Org. no. 922673160 Limited company (AS) Vefsn Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 873,000
Operating profit NOK 209,000
Equity NOK 708,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

3.M EIENDOM AS is registered as a limited company in Vefsn, Nordland with organisation number 922673160. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleievirksomhet av fast eiendom, eiendomsutvikling og alt hva som derved står i forbindelse med.”. The most recent filed accounts, for the 2025 financial year, show NOK 873,000 in revenue and NOK 209,000 in operating profit.

Key figures · 2025

Revenue
NOK 873,000
Operating profit
NOK 209,000
Equity
NOK 708,000
Est. value
NOK 805,000

Financial health · 2025

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns 3.M EIENDOM AS?

MNB HOLDING AS
3.M EIENDOM AS
NOK 873,000 rev. · NOK 209,000 profit

3.M EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 3.M EIENDOM AS

Who owns 3.M EIENDOM AS?

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

What is the revenue of 3.M EIENDOM AS?

3.M EIENDOM AS had revenue of NOK 873,000 in 2025.

Who is the general manager of 3.M EIENDOM AS?

Steinar Åkvik is registered as general manager of 3.M EIENDOM AS.

Where is 3.M EIENDOM AS based?

3.M EIENDOM AS has its business address in Mosjøen.

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.