BIZTRAC BETA
Computer programming activities

SOURCEIT AS

Org. no. 998514517 Limited company (AS) Risør Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 28,000
Equity NOK −12,000
Incorporated 2012
Share capital NOK 36,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−12k kr).

SOURCEIT AS is registered as a limited company in Risør, Agder with organisation number 998514517. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2012. Registered share capital is NOK 36,000, divided into 32609 shares. The company's stated purpose is: “Å drive utvikling og å drifte dataløsninger i skyen for bedriftskunder.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 28,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 28,000
Equity
NOK −12,000
Est. value
NOK 234,000

Financial health · 2024

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

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

Who owns SOURCEIT AS?

SIGTOR AS
SOURCEIT AS
NOK 2.1m rev. · NOK 28,000 profit

SOURCEIT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SOURCEIT AS own?

SOURCEIT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SOURCEIT AS

Who owns SOURCEIT AS?

SIGTOR AS is the largest registered owner, with 75.0%.

What is the revenue of SOURCEIT AS?

SOURCEIT AS had revenue of NOK 2.1m in 2024.

Who is the general manager of SOURCEIT AS?

Sigbjørn Tønnesland is registered as general manager of SOURCEIT AS.

Where is SOURCEIT AS based?

SOURCEIT AS has its business address in Risør.

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.