BIZTRAC BETA
Accounting and bookkeeping

PARECO ACCOUNTING AS

Org. no. 932739038 Limited company (AS) Øygarden Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 289,000
Equity NOK 230,000
Incorporated 2023
Share capital NOK 30,000

PARECO ACCOUNTING AS is registered as a limited company in Øygarden, Vestland with organisation number 932739038. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Regnskapsføring og rådgivning, samt konsulenttjenester innen økonomi og administrasjon og alt som naturlig sammenfaller med dette. Selskapet skal også gi støtte til veldedige og allmennyttige formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 289,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 289,000
Equity
NOK 230,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns PARECO ACCOUNTING AS?

PARECO INVEST AS
PARECO ACCOUNTING AS
NOK 2.9m rev. · NOK 289,000 profit

PARECO ACCOUNTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARECO ACCOUNTING AS

Who owns PARECO ACCOUNTING AS?

PARECO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of PARECO ACCOUNTING AS?

PARECO ACCOUNTING AS had revenue of NOK 2.9m in 2025.

Who is the general manager of PARECO ACCOUNTING AS?

Morten Parelius is registered as general manager of PARECO ACCOUNTING AS.

Where is PARECO ACCOUNTING AS based?

PARECO ACCOUNTING AS has its business address in Steinsland.

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.