BIZTRAC BETA
Publishing of video games

DIRTYBIT AS

Org. no. 912002942 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 36.7m
Operating profit NOK 1.8m
Equity NOK 22.6m
Incorporated 2013
Employees 17
Share capital NOK 60,000

DIRTYBIT AS is registered as a limited company in Bergen, Vestland with organisation number 912002942. The business is classified under publishing of video games (NACE 58.210). The company was incorporated in 2013 and has 17 registered employees. Registered share capital is NOK 60,000, divided into 20000000 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter å forestå utvikling, drift og salg av dataprogramvare og annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 36.7m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 36.7m
Operating profit
NOK 1.8m
Equity
NOK 22.6m
Est. value
NOK 24.8m

Financial health · 2024

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

Who owns DIRTYBIT AS?

MNV AS
DIRTYBIT AS
NOK 36.7m rev. · NOK 1.8m profit

DIRTYBIT AS has 13 registered shareholders:

All shareholders and roles →

Which companies does DIRTYBIT AS own?

DIRTYBIT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DIRTYBIT AS

Who owns DIRTYBIT AS?

MNV AS is the largest registered owner, with 34.5%.

What is the revenue of DIRTYBIT AS?

DIRTYBIT AS had revenue of NOK 36.7m in 2024.

Who is the general manager of DIRTYBIT AS?

Erlend Børslid Haugsdal is registered as general manager of DIRTYBIT AS.

Where is DIRTYBIT AS based?

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