BIZTRAC BETA
Repair and maintenance of motor vehicles

MODUM BILLAKKSENTER AS

Org. no. 998550297 Limited company (AS) Modum Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 21.4m
Operating profit NOK 1.4m
Equity NOK 3.4m
Incorporated 2012
Employees 8
Share capital NOK 30,000

MODUM BILLAKKSENTER AS is registered as a limited company in Modum, Buskerud with organisation number 998550297. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2012 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Alt som naturlig hører inn under oppretting og lakkeringsverksted. Kjøp og salg av biler. Kosmetisk bilpleie. Deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.4m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 21.4m
Operating profit
NOK 1.4m
Equity
NOK 3.4m
Est. value
NOK 7.3m

Financial health · 2024

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

Who owns MODUM BILLAKKSENTER AS?

ARNE WOLFRAM
MODUM BILLAKKSENTER AS
NOK 21.4m rev. · NOK 1.4m profit

MODUM BILLAKKSENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MODUM BILLAKKSENTER AS

Who owns MODUM BILLAKKSENTER AS?

ARNE WOLFRAM is the largest registered owner, with 90.0%.

What is the revenue of MODUM BILLAKKSENTER AS?

MODUM BILLAKKSENTER AS had revenue of NOK 21.4m in 2024.

Who is the general manager of MODUM BILLAKKSENTER AS?

Arne Wolfram is registered as general manager of MODUM BILLAKKSENTER AS.

Where is MODUM BILLAKKSENTER AS based?

MODUM BILLAKKSENTER AS has its business address in Vikersund.

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.