BIZTRAC BETA
Accounting and bookkeeping

EP REGNSKAP AS

Org. no. 986427813 Limited company (AS) Trondheim Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 8.8m
Operating profit NOK 1.8m
Equity NOK 100,000
Incorporated 2004
Employees 9
Share capital NOK 100,000

EP REGNSKAP AS is registered as a limited company in Trondheim, Trøndelag with organisation number 986427813. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2004 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Regnskapsførsel, konsulentvirksomhet, rådgivning og hva ellers faller naturlig inn i denne virksomheten, samt annen økonomisk virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.8m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 8.8m
Operating profit
NOK 1.8m
Equity
NOK 100,000
Est. value
NOK 7.5m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.5%
Not satisfactory
Equity as a share of total capital

Who owns EP REGNSKAP AS?

ESKIL PETTERSEN
EP REGNSKAP AS
NOK 8.8m rev. · NOK 1.8m profit

EP REGNSKAP AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EP REGNSKAP AS own?

EP REGNSKAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EP REGNSKAP AS

Who owns EP REGNSKAP AS?

ESKIL PETTERSEN is the largest registered owner, with 90.1%.

What is the revenue of EP REGNSKAP AS?

EP REGNSKAP AS had revenue of NOK 8.8m in 2025.

Who is the general manager of EP REGNSKAP AS?

Eskil Pettersen is registered as general manager of EP REGNSKAP AS.

Where is EP REGNSKAP AS based?

EP REGNSKAP AS has its business address in Trondheim.

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.