biztrac. BETA
COMPANY REGISTER PROFILE
925987298 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

GÅLÅSHOLMEN INFRASTRUKTUR AS

Org. no. 925987298 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 2.5m
Equity NOK 963,000
Incorporated 2020
Share capital NOK 456,000

GÅLÅSHOLMEN INFRASTRUKTUR AS is registered as a limited company in Oslo, Oslo with organisation number 925987298. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 456,000, divided into 7727 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
▲ +2 %
Operating profit
NOK 2.5m
▲ +3 %
Equity
NOK 963,000
▲ +1 %
Est. value
NOK 5.2m

Financial health · 2025

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
25.9%
Good
Equity as a share of total capital

Who owns GÅLÅSHOLMEN INFRASTRUKTUR AS?

GÅLÅSHOLMEN INFRASTRUKTUR AS
NOK 2.5m rev. · NOK 2.5m profit

GÅLÅSHOLMEN INFRASTRUKTUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GÅLÅSHOLMEN INFRASTRUKTUR AS

Who owns GÅLÅSHOLMEN INFRASTRUKTUR AS?

GÅLÅSHOLMEN INFRASTRUKTUR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GÅLÅSHOLMEN INFRASTRUKTUR AS?

GÅLÅSHOLMEN INFRASTRUKTUR AS had revenue of NOK 2.5m in 2025.

Where is GÅLÅSHOLMEN INFRASTRUKTUR AS based?

GÅLÅSHOLMEN INFRASTRUKTUR 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 03.10.2026.

Report a problem

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