BIZTRAC BETA
Computer programming activities

DBUG AS

Org. no. 919202750 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 5.0m
Incorporated 2017
Share capital NOK 75,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).
  • Nylig endring 2026-05-23 Aksjekapital registrert 2026-05-23.

DBUG AS is registered as a limited company in Asker, Akershus with organisation number 919202750. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 75,000, divided into 150 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi, samt investeringer og deltakere i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 5.0m
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
79.66
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.7%
Very good
Equity as a share of total capital

Who owns DBUG AS?

MARIUS STENSETH ERIKSRUD
DBUG AS
NOK 0 rev. · NOK −4,000 profit

DBUG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does DBUG AS own?

DBUG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DBUG AS

Who owns DBUG AS?

MARIUS STENSETH ERIKSRUD is the largest registered owner, with 50.0%.

What is the revenue of DBUG AS?

DBUG AS had revenue of NOK 0 in 2025.

Who is the general manager of DBUG AS?

Marius Stenseth Eriksrud is registered as general manager of DBUG AS.

Where is DBUG AS based?

DBUG AS has its business address in Slemmestad.

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.