biztrac. BETA
COMPANY REGISTER PROFILE
926887319 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

TALGE AS

Org. no. 926887319 Limited company (AS) Haugesund Incorporated 2021 Active
Operating profit NOK −25,000
Equity NOK −9,000
Incorporated 2021
Share capital NOK 60,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−9k kr).

TALGE AS is registered as a limited company in Haugesund, Rogaland with organisation number 926887319. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −25,000
▲ +54 %
Equity
NOK −9,000
▼ −118 %

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
-86.8%
Not satisfactory
Return on total assets
Solidity
-609.7%
Weak
Equity as a share of total capital

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

Who owns TALGE AS?

TALGE AS
· NOK −25,000 profit

TALGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TALGE AS own?

TALGE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TALGE AS

Who owns TALGE AS?

Roar Talge is the largest registered owner, with 100.0%.

Who is the general manager of TALGE AS?

Roar Talge is registered as general manager of TALGE AS.

Where is TALGE AS based?

TALGE AS has its business address in Haugesund.

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

Report a problem

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