BIZTRAC BETA
Machining of metals

GURSKØY EIENDOM AS

Org. no. 995900963 Limited company (AS) Herøy Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.5m
Equity NOK 2.9m
Incorporated 2010
Share capital NOK 156,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GURSKØY EIENDOM AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 995900963. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2010. Registered share capital is NOK 156,000, divided into 260 shares. The company's stated purpose is: “Erverv, forvaltning, utvikling og utleie av fast eiendom og annen virksomhet som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.5m
Equity
NOK 2.9m
Est. value
NOK 5.9m

Financial health · 2025

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

Who owns GURSKØY EIENDOM AS?

MYK HOLDING AS
GURSKØY EIENDOM AS
NOK 1.9m rev. · NOK 1.5m profit

GURSKØY EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GURSKØY EIENDOM AS

Who owns GURSKØY EIENDOM AS?

MYK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GURSKØY EIENDOM AS?

GURSKØY EIENDOM AS had revenue of NOK 1.9m in 2025.

Who is the general manager of GURSKØY EIENDOM AS?

Trond Myking is registered as general manager of GURSKØY EIENDOM AS.

Where is GURSKØY EIENDOM AS based?

GURSKØY EIENDOM AS has its business address in Gurskøy.

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.