BIZTRAC BETA
Rental and operating of own or leased real estate

M OG A BYGG OG EIENDOM AS

Org. no. 916160844 Limited company (AS) Flekkefjord Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 203,000
Operating profit NOK 111,000
Equity NOK −71,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

M OG A BYGG OG EIENDOM AS is registered as a limited company in Flekkefjord, Agder with organisation number 916160844. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Utleie av egen eller leid fast eiendom ellers.”. The most recent filed accounts, for the 2025 financial year, show NOK 203,000 in revenue and NOK 111,000 in operating profit.

Key figures · 2025

Revenue
NOK 203,000
Operating profit
NOK 111,000
Equity
NOK −71,000
Est. value
NOK 455,000

Financial health · 2025

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

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

Who owns M OG A BYGG OG EIENDOM AS?

EMIDBØE HOLDING AS
M OG A BYGG OG EIENDOM AS
NOK 203,000 rev. · NOK 111,000 profit

M OG A BYGG OG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about M OG A BYGG OG EIENDOM AS

Who owns M OG A BYGG OG EIENDOM AS?

EMIDBØE HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of M OG A BYGG OG EIENDOM AS?

M OG A BYGG OG EIENDOM AS had revenue of NOK 203,000 in 2025.

Where is M OG A BYGG OG EIENDOM AS based?

M OG A BYGG OG EIENDOM AS has its business address in Flekkefjord.

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.