BIZTRAC BETA
Retail sale of cultural and recreational goods n.e.c.

GRINDHEIM HOLDING AS

Org. no. 927337487 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −130
Equity NOK 96,000
Incorporated 2021
Share capital NOK 110,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−130 kr).

GRINDHEIM HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 927337487. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 2021. Registered share capital is NOK 110,000, divided into 110 shares. The company's stated purpose is: “Eierskap av aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −130 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −130
Equity
NOK 96,000
Est. value
NOK 120,000

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.5%
Weak
Equity as a share of total capital

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

Who owns GRINDHEIM HOLDING AS?

TORE GRINDHEIM
GRINDHEIM HOLDING AS
NOK 0 rev. · NOK −130 profit

GRINDHEIM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRINDHEIM HOLDING AS own?

GRINDHEIM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GRINDHEIM HOLDING AS

Who owns GRINDHEIM HOLDING AS?

TORE GRINDHEIM is the largest registered owner, with 100.0%.

What is the revenue of GRINDHEIM HOLDING AS?

GRINDHEIM HOLDING AS had revenue of NOK 0 in 2024.

Where is GRINDHEIM HOLDING AS based?

GRINDHEIM HOLDING AS has its business address in Søreidgrend.

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.