BIZTRAC BETA
Other captive investment companies

GEIRSTAD HOLDING AS

Org. no. 989265792 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 9.7m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

GEIRSTAD HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989265792. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andeler, kjøp og salg av fast eiendom, samt deltagelse i annen virksomhet med likelydende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 9.7m
Est. value
NOK 29.9m

Financial health · 2024

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

Who owns GEIRSTAD HOLDING AS?

GEIR BJØRNSTAD
GEIRSTAD HOLDING AS
NOK 0 rev. · NOK −12,000 profit

GEIRSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GEIRSTAD HOLDING AS own?

GEIRSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GEIRSTAD HOLDING AS

Who owns GEIRSTAD HOLDING AS?

GEIR BJØRNSTAD is the largest registered owner, with 100.0%.

What is the revenue of GEIRSTAD HOLDING AS?

GEIRSTAD HOLDING AS had revenue of NOK 0 in 2025.

Where is GEIRSTAD HOLDING AS based?

GEIRSTAD HOLDING AS has its business address in Trondheim.

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.