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

TALGØ-HJELLEGJERDE AS

Org. no. 932108186 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Equity NOK 5.1m
Incorporated 2022
Share capital NOK 30,000

TALGØ-HJELLEGJERDE AS is registered as a limited company in Oslo, Oslo with organisation number 932108186. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskaper og øvrige finansielle investeringer, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Equity
NOK 5.1m
▲ +4 %
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
264.58
Very good
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns TALGØ-HJELLEGJERDE AS?

TALGØ-HJELLEGJERDE AS

TALGØ-HJELLEGJERDE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TALGØ-HJELLEGJERDE AS own?

TALGØ-HJELLEGJERDE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TALGØ-HJELLEGJERDE AS

Who owns TALGØ-HJELLEGJERDE AS?

GUNN TALGØ is the largest registered owner, with 100.0%.

Where is TALGØ-HJELLEGJERDE AS based?

TALGØ-HJELLEGJERDE AS has its business address in Oslo.

Property

Business address Lille Frøens vei 2A, 0371 Oslo
Cadastral unit 301-38/48/0/0
Building Enebolig · 1 unit

4 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.