BIZTRAC BETA
Computer programming activities

SVENN AS

Org. no. 911801663 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 15.5m
Operating profit NOK −8.3m
Equity NOK 9.6m
Incorporated 2013
Employees 22
Share capital NOK 407,000

Signals

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

SVENN AS is registered as a limited company in Oslo, Oslo with organisation number 911801663. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2013 and has 22 registered employees. Registered share capital is NOK 407,000, divided into 3129125 shares. The company's stated purpose is: “Utvikling og drift av digitale løsninger samt salg av disse og deltagelse i selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.5m in revenue and NOK −8.3m in operating profit.

Key figures · 2024

Revenue
NOK 15.5m
Operating profit
NOK −8.3m
Equity
NOK 9.6m
Est. value
NOK 21.3m

Financial health · 2024

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.5%
Good
Equity as a share of total capital

Who owns SVENN AS?

NORSELAB F I SVE AS
SVENN AS
NOK 15.5m rev. · NOK −8.3m profit

SVENN AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does SVENN AS own?

SVENN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVENN AS

Who owns SVENN AS?

NORSELAB F I SVE AS is the largest registered owner, with 37.4%.

What is the revenue of SVENN AS?

SVENN AS had revenue of NOK 15.5m in 2024.

Who is the general manager of SVENN AS?

Sondre Blaasmo is registered as general manager of SVENN AS.

Where is SVENN AS based?

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