BIZTRAC BETA
Accounting and bookkeeping

BRUMUNDDAL REGNSKAP AS

Org. no. 979881401 Limited company (AS) Ringsaker Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 13.0m
Operating profit NOK 1.9m
Equity NOK 1.1m
Incorporated 1998
Employees 11
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-06-03 Adresseendring registrert 2026-06-03.

BRUMUNDDAL REGNSKAP AS is registered as a limited company in Ringsaker, Innlandet with organisation number 979881401. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1998 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Regnskapsføring for andre, samt økonomi og rådgivningstjenester til små og mellomstore bedrifter.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.0m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 13.0m
Operating profit
NOK 1.9m
Equity
NOK 1.1m
Est. value
NOK 9.8m

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.2%
Good
Equity as a share of total capital

Who owns BRUMUNDDAL REGNSKAP AS?

WLC AS
BRUMUNDDAL REGNSKAP AS
NOK 13.0m rev. · NOK 1.9m profit

BRUMUNDDAL REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRUMUNDDAL REGNSKAP AS

Who owns BRUMUNDDAL REGNSKAP AS?

WLC AS is the largest registered owner, with 100.0%.

What is the revenue of BRUMUNDDAL REGNSKAP AS?

BRUMUNDDAL REGNSKAP AS had revenue of NOK 13.0m in 2025.

Who is the general manager of BRUMUNDDAL REGNSKAP AS?

Jørn Wiik is registered as general manager of BRUMUNDDAL REGNSKAP AS.

Where is BRUMUNDDAL REGNSKAP AS based?

BRUMUNDDAL REGNSKAP AS has its business address in Brumunddal.

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.