BIZTRAC BETA
Accounting and bookkeeping

WEPE REGNSKAP AS

Org. no. 976095057 Limited company (AS) Aurskog-Høland Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 53.4m
Operating profit NOK 6.7m
Equity NOK 5.7m
Incorporated 1996
Employees 40
Share capital NOK 45,000

WEPE REGNSKAP AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 976095057. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1996 and has 40 registered employees. Registered share capital is NOK 45,000, divided into 900 shares. The company's stated purpose is: “Regnskapsføring og økonomisk bistand, samt hva som naturlig måtte stå i forbindelse med dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 53.4m in revenue and NOK 6.7m in operating profit.

Key figures · 2025

Revenue
NOK 53.4m
Operating profit
NOK 6.7m
Equity
NOK 5.7m
Est. value
NOK 36.2m

Financial health · 2025

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.8%
Good
Equity as a share of total capital

Who owns WEPE REGNSKAP AS?

AURSKOG SPAREBANK
WEPE REGNSKAP AS
NOK 53.4m rev. · NOK 6.7m profit

WEPE REGNSKAP AS has 5 registered shareholders:

All shareholders and roles →

Which companies does WEPE REGNSKAP AS own?

WEPE REGNSKAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WEPE REGNSKAP AS

Who owns WEPE REGNSKAP AS?

AURSKOG SPAREBANK is the largest registered owner, with 34.0%.

What is the revenue of WEPE REGNSKAP AS?

WEPE REGNSKAP AS had revenue of NOK 53.4m in 2025.

Who is the general manager of WEPE REGNSKAP AS?

Anders Moen Lysaker is registered as general manager of WEPE REGNSKAP AS.

Where is WEPE REGNSKAP AS based?

WEPE REGNSKAP AS has its business address in Bjørkelangen.

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.