BIZTRAC BETA
Accounting and bookkeeping

ECCCO REGNSKAP AS

Org. no. 932752468 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 406,000
Equity NOK 298,000
Incorporated 2023
Share capital NOK 30,000

ECCCO REGNSKAP AS is registered as a limited company in Tønsberg, Vestfold with organisation number 932752468. 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 60 shares. The company's stated purpose is: “Regnskapsføring for andre, rådgivning, kursing, bistand ved etablering samt andre aktiviteter som naturlig faller sammen med dette, deltagelse i andre selskap med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 406,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 406,000
Equity
NOK 298,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns ECCCO REGNSKAP AS?

8 HOLDING AS
ECCCO REGNSKAP AS
NOK 1.1m rev. · NOK 406,000 profit

ECCCO REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ECCCO REGNSKAP AS

Who owns ECCCO REGNSKAP AS?

8 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ECCCO REGNSKAP AS?

ECCCO REGNSKAP AS had revenue of NOK 1.1m in 2024.

Who is the general manager of ECCCO REGNSKAP AS?

Lisa Gjessing is registered as general manager of ECCCO REGNSKAP AS.

Where is ECCCO REGNSKAP AS based?

ECCCO REGNSKAP AS has its business address in Tønsberg.

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.