biztrac. BETA
COMPANY REGISTER PROFILE
933822788 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

MYRHAUGEN AS

Org. no. 933822788 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 360,000
Operating profit NOK 319,000
Equity NOK 348,000
Incorporated 2024
Share capital NOK 30,000

MYRHAUGEN AS is registered as a limited company in Oslo, Oslo with organisation number 933822788. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, investeringer i verdipapirer, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 360,000 in revenue and NOK 319,000 in operating profit.

Key figures · 2025

Revenue
NOK 360,000
▲ +243 %
Operating profit
NOK 319,000
▲ +319 %
Equity
NOK 348,000
▲ +267 %
Est. value
NOK 665,000

Financial health · 2025

Liquidity
25.83
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
1.5%
Not satisfactory
Equity as a share of total capital

Who owns MYRHAUGEN AS?

MYRHAUGEN AS
NOK 360,000 rev. · NOK 319,000 profit

MYRHAUGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MYRHAUGEN AS

Who owns MYRHAUGEN AS?

LG BYGG & EIENDOMSUTVIKLING AS is the largest registered owner, with 50.0%.

What is the revenue of MYRHAUGEN AS?

MYRHAUGEN AS had revenue of NOK 360,000 in 2025.

Who is the general manager of MYRHAUGEN AS?

Andre Farstad is registered as general manager of MYRHAUGEN AS.

Where is MYRHAUGEN AS based?

MYRHAUGEN AS has its business address in Oslo.

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.