BIZTRAC BETA
Activities of advertising agencies

MYLDER EIENDOM AS

Org. no. 985229724 Limited company (AS) Trondheim Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 360,000
Operating profit NOK 44,000
Equity NOK −172,000
Incorporated 2002
Share capital NOK 200,000

Signals

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

MYLDER EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 985229724. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Investere i eiendom, herunder aksjer, lån og andeler i eiendomsselskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 360,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2024

Revenue
NOK 360,000
Operating profit
NOK 44,000
Equity
NOK −172,000
Est. value
NOK 177,000

Financial health · 2024

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

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

Who owns MYLDER EIENDOM AS?

SANUK AS
MYLDER EIENDOM AS
NOK 360,000 rev. · NOK 44,000 profit

MYLDER EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MYLDER EIENDOM AS own?

MYLDER EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MYLDER EIENDOM AS

Who owns MYLDER EIENDOM AS?

SANUK AS is the largest registered owner, with 50.0%.

What is the revenue of MYLDER EIENDOM AS?

MYLDER EIENDOM AS had revenue of NOK 360,000 in 2024.

Where is MYLDER EIENDOM AS based?

MYLDER EIENDOM AS has its business address in Trondheim.

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.