BIZTRAC BETA
Uoppgitt

GLENN HOVLAND HOLDING AS

Org. no. 928884228 Limited company (AS) Bjørnafjorden Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 50,000
Operating profit NOK 41,000
Equity NOK 77,000
Incorporated 2022
Share capital NOK 30,000

GLENN HOVLAND HOLDING AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 928884228. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å være et holdingselskap som investerer i aksjer og fast eiendom, samt annet som er nært beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 50,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 50,000
Operating profit
NOK 41,000
Equity
NOK 77,000
Est. value
NOK 167,000

Financial health · 2025

Liquidity
4.62
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
81.8%
Weak
Equity as a share of total capital

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

Who owns GLENN HOVLAND HOLDING AS?

GLENN HOVLAND
GLENN HOVLAND HOLDING AS
NOK 50,000 rev. · NOK 41,000 profit

GLENN HOVLAND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GLENN HOVLAND HOLDING AS own?

GLENN HOVLAND HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GLENN HOVLAND HOLDING AS

Who owns GLENN HOVLAND HOLDING AS?

GLENN HOVLAND is the largest registered owner, with 100.0%.

What is the revenue of GLENN HOVLAND HOLDING AS?

GLENN HOVLAND HOLDING AS had revenue of NOK 50,000 in 2025.

Where is GLENN HOVLAND HOLDING AS based?

GLENN HOVLAND HOLDING AS has its business address in Hagavik.

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.