BIZTRAC BETA
Accounting and bookkeeping

MOELV REGNSKAPSBYRÅ AS

Org. no. 932039214 Limited company (AS) Ringsaker Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 18.6m
Operating profit NOK 3.6m
Equity NOK 1.1m
Incorporated 2023
Employees 13
Share capital NOK 525,000

MOELV REGNSKAPSBYRÅ AS is registered as a limited company in Ringsaker, Innlandet with organisation number 932039214. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023 and has 13 registered employees. Registered share capital is NOK 525,000, divided into 300 shares. The company's stated purpose is: “Regnskapstjenester- og økonomitjenester av enhver art. Selskapet kan videre investere i aksjer og annen fast eiendom og drive utleie av personell.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.6m in revenue and NOK 3.6m in operating profit.

Key figures · 2024

Revenue
NOK 18.6m
Operating profit
NOK 3.6m
Equity
NOK 1.1m
Est. value
NOK 16.1m

Financial health · 2024

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

Who owns MOELV REGNSKAPSBYRÅ AS?

B. NORDAHL AS
MOELV REGNSKAPSBYRÅ AS
NOK 18.6m rev. · NOK 3.6m profit

MOELV REGNSKAPSBYRÅ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOELV REGNSKAPSBYRÅ AS

Who owns MOELV REGNSKAPSBYRÅ AS?

B. NORDAHL AS is the largest registered owner, with 33.3%.

What is the revenue of MOELV REGNSKAPSBYRÅ AS?

MOELV REGNSKAPSBYRÅ AS had revenue of NOK 18.6m in 2024.

Who is the general manager of MOELV REGNSKAPSBYRÅ AS?

Svein Tore Løkken is registered as general manager of MOELV REGNSKAPSBYRÅ AS.

Where is MOELV REGNSKAPSBYRÅ AS based?

MOELV REGNSKAPSBYRÅ AS has its business address in Moelv.

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.