BIZTRAC BETA
Uoppgitt

GLTR HOLDING AS

Org. no. 927467615 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 25,000
Operating profit NOK 24,000
Equity NOK 40,000
Incorporated 2021
Share capital NOK 30,000

GLTR HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 927467615. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 25,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 25,000
Operating profit
NOK 24,000
Equity
NOK 40,000
Est. value
NOK 73,000

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GLTR HOLDING AS?

ESPEN HUNDSNES GRØVLEN
GLTR HOLDING AS
NOK 25,000 rev. · NOK 24,000 profit

GLTR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GLTR HOLDING AS own?

GLTR HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about GLTR HOLDING AS

Who owns GLTR HOLDING AS?

ESPEN HUNDSNES GRØVLEN is the largest registered owner, with 100.0%.

What is the revenue of GLTR HOLDING AS?

GLTR HOLDING AS had revenue of NOK 25,000 in 2025.

Where is GLTR HOLDING AS based?

GLTR HOLDING AS has its business address in Bergen.

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.