BIZTRAC BETA
Rental and operating of own or leased real estate

FIOLVEGEN TROMSØ AS

Org. no. 922717109 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 2.4m
Equity NOK 3.7m
Incorporated 2019
Share capital NOK 80,000

FIOLVEGEN TROMSØ AS is registered as a limited company in Oslo, Oslo with organisation number 922717109. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 80,000, divided into 40000 shares. The company's stated purpose is: “Å drive med kjøp og salg samt utleie av eiendom og det som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 2.4m
Equity
NOK 3.7m
Est. value
NOK 6.5m

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.7%
Satisfactory
Equity as a share of total capital

Who owns FIOLVEGEN TROMSØ AS?

GK GRUPPEN EIENDOM AS
FIOLVEGEN TROMSØ AS
NOK 2.9m rev. · NOK 2.4m profit

FIOLVEGEN TROMSØ AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FIOLVEGEN TROMSØ AS er morselskap for 5 datterselskaper:

Frequently asked questions about FIOLVEGEN TROMSØ AS

Who owns FIOLVEGEN TROMSØ AS?

GK GRUPPEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FIOLVEGEN TROMSØ AS?

FIOLVEGEN TROMSØ AS had revenue of NOK 2.9m in 2024.

Who is the general manager of FIOLVEGEN TROMSØ AS?

Christopher John Karlsen is registered as general manager of FIOLVEGEN TROMSØ AS.

Where is FIOLVEGEN TROMSØ AS based?

FIOLVEGEN TROMSØ 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.