BIZTRAC BETA
Computer programming activities

DREIS AS

Org. no. 925193836 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 4,000
Operating profit NOK −117,000
Equity NOK −399,000
Incorporated 2020
Share capital NOK 300,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−399k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−117k kr).

DREIS AS is registered as a limited company in Bergen, Vestland with organisation number 925193836. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Utvikling av programvare og tekst innen kunnskapsbaserte konkurranser, samt deltakelse i andre selskap gjennom aksjeeie og utvikling av tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4,000 in revenue and NOK −117,000 in operating profit.

Key figures · 2024

Revenue
NOK 4,000
Operating profit
NOK −117,000
Equity
NOK −399,000

Financial health · 2024

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

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

Who owns DREIS AS?

STEG AS
DREIS AS
NOK 4,000 rev. · NOK −117,000 profit

DREIS AS has 7 registered shareholders:

All shareholders and roles →

Which companies does DREIS AS own?

DREIS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DREIS AS

Who owns DREIS AS?

STEG AS is the largest registered owner, with 38.0%.

What is the revenue of DREIS AS?

DREIS AS had revenue of NOK 4,000 in 2024.

Where is DREIS AS based?

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