biztrac. BETA
COMPANY REGISTER PROFILE
930898953 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

MONSEN EIENDOM AS

Org. no. 930898953 Limited company (AS) Øygarden Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 748,000
Operating profit NOK 249,000
Equity NOK −195,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

MONSEN EIENDOM AS is registered as a limited company in Øygarden, Vestland with organisation number 930898953. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av fast eiendom, herunder kjøp, utleie og salg av fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 748,000 in revenue and NOK 249,000 in operating profit.

Key figures · 2025

Revenue
NOK 748,000
▲ +284 %
Operating profit
NOK 249,000
▲ +106 %
Equity
NOK −195,000
▼ −1437 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
3.9%
Weak
Return on total assets
Solidity
-2.6%
Weak
Equity as a share of total capital

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

Who owns MONSEN EIENDOM AS?

MONSEN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MONSEN EIENDOM AS

Who owns MONSEN EIENDOM AS?

RUNE MONSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of MONSEN EIENDOM AS?

MONSEN EIENDOM AS had revenue of NOK 748,000 in 2025.

Where is MONSEN EIENDOM AS based?

MONSEN EIENDOM AS has its business address in Rong.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.