biztrac. BETA
COMPANY REGISTER PROFILE
913823931 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TOTAL BETONG HOLDING AS

Org. no. 913823931 Limited company (AS) Time Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 14.4m
Incorporated 2014
Share capital NOK 200,000

Signals

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

TOTAL BETONG HOLDING AS is registered as a limited company in Time, Rogaland with organisation number 913823931. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Investering og forvaltning av aksjer og andre eiendeler, herunder deltakelse i andre selskaper, samt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −28,000
▲ +31 %
Equity
NOK 14.4m
▼ −15 %
Est. value
NOK 15.3m

Financial health · 2025

Liquidity
0.77
Weak
Current assets ÷ current liabilities
Profitability
7.8%
Satisfactory
Return on total assets
Solidity
48.3%
Very good
Equity as a share of total capital

Who owns TOTAL BETONG HOLDING AS?

TOTAL BETONG HOLDING AS has 6 registered shareholders:

All shareholders and roles →

Which companies does TOTAL BETONG HOLDING AS own?

TOTAL BETONG HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TOTAL BETONG HOLDING AS

Who owns TOTAL BETONG HOLDING AS?

ORSTAD RÅDGIVNING AS is the largest registered owner, with 24.5%.

Who is the general manager of TOTAL BETONG HOLDING AS?

Kurt Helland is registered as general manager of TOTAL BETONG HOLDING AS.

Where is TOTAL BETONG HOLDING AS based?

TOTAL BETONG HOLDING AS has its business address in Bryne.

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.