BIZTRAC BETA
Construction of residential and non-residential buildings

T. SKARE HOLDING AS

Org. no. 918912088 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −40,000
Equity NOK 344,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

T. SKARE HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 918912088. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer, verdipapir og andre foretak med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −40,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −40,000
Equity
NOK 344,000
Est. value
NOK 352,000

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.8%
Good
Equity as a share of total capital

Who owns T. SKARE HOLDING AS?

TAGE WÆRDAHL SKARE
T. SKARE HOLDING AS
NOK 0 rev. · NOK −40,000 profit

T. SKARE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does T. SKARE HOLDING AS own?

T. SKARE HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about T. SKARE HOLDING AS

Who owns T. SKARE HOLDING AS?

TAGE WÆRDAHL SKARE is the largest registered owner, with 100.0%.

What is the revenue of T. SKARE HOLDING AS?

T. SKARE HOLDING AS had revenue of NOK 0 in 2024.

Where is T. SKARE HOLDING AS based?

T. SKARE HOLDING AS has its business address in Flaktveit.

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.