BIZTRAC BETA
COMPANY REGISTER PROFILE
936768849 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

GTAHI AS

Org. no. 936768849 Limited company (AS) Ringerike Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 22.7m
Incorporated 2025
Share capital NOK 60,000

GTAHI AS is registered as a limited company in Ringerike, Buskerud with organisation number 936768849. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Investeringer i andre selskap mv.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 22.7m
Est. value
NOK 26.7m

Financial health · 2025

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

Who owns GTAHI AS?

GTAHI AS
NOK 0 rev. · NOK 0 profit

GTAHI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GTAHI AS

Who owns GTAHI AS?

GRO SØNSTEBY STRANDE is the largest registered owner, with 100.0%.

What is the revenue of GTAHI AS?

GTAHI AS had revenue of NOK 0 in 2025.

Where is GTAHI AS based?

GTAHI AS has its business address in Hønefoss.

Property

Business address Nordre Ringåsen 36, 3512 Hønefoss
Cadastral unit 3305-40/26/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.