BIZTRAC BETA
Other real estate activities on a fee or contract basis

GULLMYR EIENDOM AS

Org. no. 930473278 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −607,000
Equity NOK 8.3m
Incorporated 2022
Share capital NOK 216,000

Signals

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

GULLMYR EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 930473278. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2022. Registered share capital is NOK 216,000, divided into 100 shares. The company's stated purpose is: “Forvaltning av fast eiendom, og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −607,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −607,000
Equity
NOK 8.3m
Est. value
NOK 7.7m

Financial health · 2025

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

Who owns GULLMYR EIENDOM AS?

TOM MYRVANG
GULLMYR EIENDOM AS
NOK 1.3m rev. · NOK −607,000 profit

GULLMYR EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GULLMYR EIENDOM AS

Who owns GULLMYR EIENDOM AS?

TOM MYRVANG is the largest registered owner, with 30.0%.

What is the revenue of GULLMYR EIENDOM AS?

GULLMYR EIENDOM AS had revenue of NOK 1.3m in 2025.

Who is the general manager of GULLMYR EIENDOM AS?

Vigdis Gulbæk Enersen is registered as general manager of GULLMYR EIENDOM AS.

Where is GULLMYR EIENDOM AS based?

GULLMYR EIENDOM AS has its business address in Fetsund.

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.