BIZTRAC BETA
Computer programming activities

TELESCOPECO AS

Org. no. 927998068 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK −3.8m
Equity NOK 1.8m
Incorporated 2021
Employees 14
Share capital NOK 48,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,8 mill kr).

TELESCOPECO AS is registered as a limited company in Oslo, Oslo with organisation number 927998068. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021 and has 14 registered employees. Registered share capital is NOK 48,000, divided into 476832 shares. The company's stated purpose is: “Utvikle og selge programvare innenfor informasjonsteknologi, samt levere generelle konsulenttjenester, og alt som kan knyttes til denne type virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK −3.8m in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK −3.8m
Equity
NOK 1.8m
Est. value
NOK 6.1m

Financial health · 2024

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

Who owns TELESCOPECO AS?

DIAMOND HOLDINGS AS
TELESCOPECO AS
NOK 3.8m rev. · NOK −3.8m profit

TELESCOPECO AS has 13 registered shareholders:

All shareholders and roles →

Frequently asked questions about TELESCOPECO AS

Who owns TELESCOPECO AS?

DIAMOND HOLDINGS AS is the largest registered owner, with 20.1%.

What is the revenue of TELESCOPECO AS?

TELESCOPECO AS had revenue of NOK 3.8m in 2024.

Who is the general manager of TELESCOPECO AS?

Gustav Haaland is registered as general manager of TELESCOPECO AS.

Where is TELESCOPECO AS based?

TELESCOPECO AS has its business address in Oslo.

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.