biztrac. BETA
COMPANY REGISTER PROFILE
986818677 ORG. NO. 2022 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA

Org. no. 986818677 General partnership with shared liability (DA) Larvik Incorporated 2004 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 617,000
Incorporated 2004

Signals

1 flags
  • Driftsunderskudd 2022 Siste driftsresultat er negativt (−5k kr).

VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA is registered as a general partnership with shared liability in Larvik, Vestfold with organisation number 986818677. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2004. The company's stated purpose is: “Økonomivirksomhet, levere tjenester innenfor regnskap, skatt og økonomikonsultasjon, investere i andre selskaper og alt som da naturlig faller inn under dette. og virksomhet som står i forbindelse med dette.”.

Key figures · 2022

Operating profit
NOK −5,000
▼ −583 %
Equity
NOK 617,000
▼ −1 %
Est. value
NOK 333,000

Financial health · 2022

Liquidity
-124.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.1%
Very good
Equity as a share of total capital

Who owns VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA?

No shareholders are registered for VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA own?

VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA

Where is VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA based?

VESTFOLD OG TELEMARK REGNSKAPSKONTOR DA has its business address in Kvelde.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.