BIZTRAC BETA
Development of building projects

MADSTUNET EIGEDOM AS

Org. no. 998057736 Limited company (AS) Øygarden Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 83,000
Operating profit NOK −4,000
Equity NOK 73,000
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

MADSTUNET EIGEDOM AS is registered as a limited company in Øygarden, Vestland with organisation number 998057736. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive eiendomsutvikling og tilhørende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 83,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 83,000
Operating profit
NOK −4,000
Equity
NOK 73,000
Est. value
NOK 174,000

Financial health · 2025

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

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

Who owns MADSTUNET EIGEDOM AS?

MADSTUNET AS
MADSTUNET EIGEDOM AS
NOK 83,000 rev. · NOK −4,000 profit

MADSTUNET EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MADSTUNET EIGEDOM AS

Who owns MADSTUNET EIGEDOM AS?

MADSTUNET AS is the largest registered owner, with 100.0%.

What is the revenue of MADSTUNET EIGEDOM AS?

MADSTUNET EIGEDOM AS had revenue of NOK 83,000 in 2025.

Who is the general manager of MADSTUNET EIGEDOM AS?

Even Lægreid is registered as general manager of MADSTUNET EIGEDOM AS.

Where is MADSTUNET EIGEDOM AS based?

MADSTUNET EIGEDOM AS has its business address in Ågotnes.

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.