BIZTRAC BETA
Wired, wireless, and satellite telecommunication activities

ETCOM AS

Org. no. 934244052 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 727,000
Operating profit NOK 21,000
Equity NOK 46,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-16 Adresseendring registrert 2026-03-16.

ETCOM AS is registered as a limited company in Oslo, Oslo with organisation number 934244052. The business is classified under wired, wireless, and satellite telecommunication activities (NACE 61.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kabelbasert telekommunikasjon, bygging av anlegg for elektrisitet og telekommunikasjon og dertil naturlig tilhørende virksomhet, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 727,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2025

Revenue
NOK 727,000
Operating profit
NOK 21,000
Equity
NOK 46,000
Est. value
NOK 199,000

Financial health · 2024

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ETCOM AS?

HRVOJE CIK
ETCOM AS
NOK 727,000 rev. · NOK 21,000 profit

ETCOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ETCOM AS

Who owns ETCOM AS?

HRVOJE CIK is the largest registered owner, with 50.0%.

What is the revenue of ETCOM AS?

ETCOM AS had revenue of NOK 727,000 in 2025.

Who is the general manager of ETCOM AS?

Hrvoje Cik is registered as general manager of ETCOM AS.

Where is ETCOM AS based?

ETCOM 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.