BIZTRAC BETA
Restaurant activities

TAALESEN HOLDING AS

Org. no. 988943428 Limited company (AS) Ullensaker Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 96,000
Operating profit NOK −716,000
Equity NOK 2.3m
Incorporated 2005
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−716k kr).

TAALESEN HOLDING AS is registered as a limited company in Ullensaker, Akershus with organisation number 988943428. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 500000 shares. The company's stated purpose is: “Kjøp, salg og investeringer i andre selskaper og verdipapairer samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 96,000 in revenue and NOK −716,000 in operating profit.

Key figures · 2024

Revenue
NOK 96,000
Operating profit
NOK −716,000
Equity
NOK 2.3m
Est. value
NOK 3.1m

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.5%
Good
Equity as a share of total capital

Who owns TAALESEN HOLDING AS?

TOR CHRISTIAN TAALESEN
TAALESEN HOLDING AS
NOK 96,000 rev. · NOK −716,000 profit

TAALESEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TAALESEN HOLDING AS own?

TAALESEN HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about TAALESEN HOLDING AS

Who owns TAALESEN HOLDING AS?

TOR CHRISTIAN TAALESEN is the largest registered owner, with 100.0%.

What is the revenue of TAALESEN HOLDING AS?

TAALESEN HOLDING AS had revenue of NOK 96,000 in 2024.

Where is TAALESEN HOLDING AS based?

TAALESEN HOLDING AS has its business address in Jessheim.

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

Report a problem

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