BIZTRAC BETA
Uoppgitt

MYRLAND AS

Org. no. 934308670 Limited company (AS) Tromsø Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 35,000
Incorporated 2024
Share capital NOK 50,000

Signals

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

MYRLAND AS is registered as a limited company in Tromsø, Troms with organisation number 934308670. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 35,000
Est. value
NOK 42,000

Financial health · 2025

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

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

Who owns MYRLAND AS?

RUNE KRISTOFFER MYRLAND
MYRLAND AS
NOK 0 rev. · NOK −9,000 profit

MYRLAND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MYRLAND AS own?

MYRLAND AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MYRLAND AS

Who owns MYRLAND AS?

RUNE KRISTOFFER MYRLAND is the largest registered owner, with 100.0%.

What is the revenue of MYRLAND AS?

MYRLAND AS had revenue of NOK 0 in 2025.

Where is MYRLAND AS based?

MYRLAND AS has its business address in Tromsø.

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.