BIZTRAC BETA
Computer programming activities

SKYTTEL AS

Org. no. 925730289 Limited company (AS) Bergen Incorporated 1953 Active
Ownership graph ↗
Revenue 2024 NOK 81.1m
Operating profit NOK 11.3m
Equity NOK 64.9m
Incorporated 1953
Employees 49
Share capital NOK 200,000

SKYTTEL AS is registered as a limited company in Bergen, Vestland with organisation number 925730289. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 1953 and has 49 registered employees. Registered share capital is NOK 200,000, divided into 3300 shares. The company's stated purpose is: “Virksomhet relatert til systemløsninger, driftstjenester og kundetjenester innen betalingsformidling, innfordring og rapportering innen transportsektoren. I tillegg skal selskapet kunne tilby tilleggstjenester fra andre sektorer knyttet til selskapets teknologiske løsninger.”. The most recent filed accounts, for the 2024 financial year, show NOK 81.1m in revenue and NOK 11.3m in operating profit.

Key figures · 2024

Revenue
NOK 81.1m
Operating profit
NOK 11.3m
Equity
NOK 64.9m
Est. value
NOK 124.7m

Financial health · 2024

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

Who owns SKYTTEL AS?

ROGALAND FYLKESKOMMUNE
SKYTTEL AS
NOK 81.1m rev. · NOK 11.3m profit

SKYTTEL AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SKYTTEL AS own?

SKYTTEL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SKYTTEL AS

Who owns SKYTTEL AS?

ROGALAND FYLKESKOMMUNE is the largest registered owner, with 33.3%.

What is the revenue of SKYTTEL AS?

SKYTTEL AS had revenue of NOK 81.1m in 2024.

Where is SKYTTEL AS based?

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