BIZTRAC BETA
Rental and operating of own or leased real estate

GJELSVIK EIGEDOM AS

Org. no. 888966722 Limited company (AS) Volda Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 555,000
Operating profit NOK 304,000
Equity NOK 2.9m
Incorporated 2005
Share capital NOK 700,000

GJELSVIK EIGEDOM AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 888966722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 700,000, divided into 700 shares. The company's stated purpose is: “Selskapet sitt føremål er kjøp, sal, drift, utleige og oppføring av fast eigedom, herunder deltaking i andre selskap med liknande føremål.”. The most recent filed accounts, for the 2025 financial year, show NOK 555,000 in revenue and NOK 304,000 in operating profit.

Key figures · 2025

Revenue
NOK 555,000
Operating profit
NOK 304,000
Equity
NOK 2.9m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns GJELSVIK EIGEDOM AS?

JON EINAR GJELSVIK
GJELSVIK EIGEDOM AS
NOK 555,000 rev. · NOK 304,000 profit

GJELSVIK EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GJELSVIK EIGEDOM AS own?

GJELSVIK EIGEDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GJELSVIK EIGEDOM AS

Who owns GJELSVIK EIGEDOM AS?

JON EINAR GJELSVIK is the largest registered owner, with 50.0%.

What is the revenue of GJELSVIK EIGEDOM AS?

GJELSVIK EIGEDOM AS had revenue of NOK 555,000 in 2025.

Where is GJELSVIK EIGEDOM AS based?

GJELSVIK EIGEDOM AS has its business address in Bjørke.

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.