BIZTRAC BETA
Computer consultancy and computer facilities management activities

TUNETEK AS

Org. no. 925083704 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 56,000
Equity NOK 62,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-10 Adresseendring registrert 2026-06-10.

TUNETEK AS is registered as a limited company in Bergen, Vestland with organisation number 925083704. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive konsulentvirksomhet tilknyttet informasjonsteknologi, samt delta i virksomhet med beslektet type aktivitet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 56,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 56,000
Equity
NOK 62,000
Est. value
NOK 355,000

Financial health · 2024

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

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

Who owns TUNETEK AS?

HÅVARD INSTEFJORD
TUNETEK AS
NOK 1.3m rev. · NOK 56,000 profit

TUNETEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TUNETEK AS

Who owns TUNETEK AS?

HÅVARD INSTEFJORD is the largest registered owner, with 100.0%.

What is the revenue of TUNETEK AS?

TUNETEK AS had revenue of NOK 1.3m in 2024.

Who is the general manager of TUNETEK AS?

Håvard Instefjord is registered as general manager of TUNETEK AS.

Where is TUNETEK AS based?

TUNETEK AS has its business address in Bergen.

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.