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

TARALDSET HOLDING AS

Org. no. 989053337 Limited company (AS) Lillestrøm Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −1.9m
Equity NOK 87.4m
Incorporated 2005
Share capital NOK 1.2m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,9 mill kr).

TARALDSET HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 989053337. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. Registered share capital is NOK 1.2m, divided into 125 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder verdipapirer, langsiktig investeringer i fast eiendom og finansielle instrumenter og annet som står i naturlig sammenheng med dette.”.

Key figures · 2025

Operating profit
NOK −1.9m
▼ −150 %
Equity
NOK 87.4m
▼ −1 %
Est. value
NOK 40.2m

Financial health · 2025

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
3.1%
Weak
Return on total assets
Solidity
36.7%
Good
Equity as a share of total capital

Who owns TARALDSET HOLDING AS?

TARALDSET HOLDING AS
· NOK −1.9m profit

TARALDSET HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TARALDSET HOLDING AS own?

TARALDSET HOLDING AS holds stakes in 19 companies:

See the full ownership structure →

Group structure

TARALDSET HOLDING AS er morselskap for 24 datterselskaper:

Frequently asked questions about TARALDSET HOLDING AS

Who owns TARALDSET HOLDING AS?

Tor Taraldset is the largest registered owner, with 92.0%.

Where is TARALDSET HOLDING AS based?

TARALDSET HOLDING AS has its business address in Lillestrøm.

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.