BIZTRAC BETA
Other technical consultancy

TO. G HOLDING AS

Org. no. 994937219 Limited company (AS) Øvre Eiker Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 3.8m
Incorporated 2009
Share capital NOK 227,000

Signals

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

TO. G HOLDING AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 994937219. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2009. Registered share capital is NOK 227,000, divided into 226975 shares. The company's stated purpose is: “Investere i andre selskaper og eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 3.8m
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns TO. G HOLDING AS?

THOMAS HORNE OLAUSSEN
TO. G HOLDING AS
NOK 0 rev. · NOK −16,000 profit

TO. G HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TO. G HOLDING AS own?

TO. G HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TO. G HOLDING AS

Who owns TO. G HOLDING AS?

THOMAS HORNE OLAUSSEN is the largest registered owner, with 100.0%.

What is the revenue of TO. G HOLDING AS?

TO. G HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of TO. G HOLDING AS?

Thomas Horne Olaussen is registered as general manager of TO. G HOLDING AS.

Where is TO. G HOLDING AS based?

TO. G HOLDING AS has its business address in Fiskum.

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.