BIZTRAC BETA
Other specialised construction activities n.e.c.

TELSTØ HOLDING AS

Org. no. 929005546 Limited company (AS) Kvam Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 1.8m
Incorporated 2022
Share capital NOK 60,000

Signals

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

TELSTØ HOLDING AS is registered as a limited company in Kvam, Vestland with organisation number 929005546. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Forestå investeringsvirksomhet, herunder investeringer i aksjer, verdipapirer og eiendom, samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 1.8m
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
94.6%
Very good
Equity as a share of total capital

Who owns TELSTØ HOLDING AS?

SVEINUNG MÆLAND
TELSTØ HOLDING AS
NOK 0 rev. · NOK −15,000 profit

TELSTØ HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TELSTØ HOLDING AS own?

TELSTØ HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TELSTØ HOLDING AS

Who owns TELSTØ HOLDING AS?

SVEINUNG MÆLAND is the largest registered owner, with 100.0%.

What is the revenue of TELSTØ HOLDING AS?

TELSTØ HOLDING AS had revenue of NOK 0 in 2025.

Where is TELSTØ HOLDING AS based?

TELSTØ HOLDING AS has its business address in Øystese.

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.