BIZTRAC BETA
Accounting and bookkeeping

G. EIENDOM AS

Org. no. 988884480 Limited company (AS) Tromsø Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 933,000
Operating profit NOK 329,000
Equity NOK 9.9m
Incorporated 2005
Share capital NOK 200,000

G. EIENDOM AS is registered as a limited company in Tromsø, Troms with organisation number 988884480. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Investeringsvirksomhet, samt annen virksomhet som står i forbindelse hermed. Selskapet skal også kunne delta i andre selskaper med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 933,000 in revenue and NOK 329,000 in operating profit.

Key figures · 2025

Revenue
NOK 933,000
Operating profit
NOK 329,000
Equity
NOK 9.9m
Est. value
NOK 6.5m

Financial health · 2025

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

Who owns G. EIENDOM AS?

SVEIN KRISTIAN GABRIELSEN
G. EIENDOM AS
NOK 933,000 rev. · NOK 329,000 profit

G. EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does G. EIENDOM AS own?

G. EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about G. EIENDOM AS

Who owns G. EIENDOM AS?

SVEIN KRISTIAN GABRIELSEN is the largest registered owner, with 100.0%.

What is the revenue of G. EIENDOM AS?

G. EIENDOM AS had revenue of NOK 933,000 in 2025.

Who is the general manager of G. EIENDOM AS?

Svein Kristian Gabrielsen is registered as general manager of G. EIENDOM AS.

Where is G. EIENDOM AS based?

G. EIENDOM 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.