biztrac. BETA
COMPANY REGISTER PROFILE
980166252 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

KJELSÅSVEIEN 168 DA

Org. no. 980166252 General partnership with shared liability (DA) Tønsberg Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −63,000
Equity NOK −580,000
Incorporated 1998

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−580k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−63k kr).

KJELSÅSVEIEN 168 DA is registered as a general partnership with shared liability in Tønsberg, Vestfold with organisation number 980166252. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1998. The company's stated purpose is: “Investering i fast eiendom fast eiendom, herunder investering i selskaper som eier eiendom, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −63,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
▲ +0 %
Operating profit
NOK −63,000
▼ −31 %
Equity
NOK −580,000
▼ −30 %

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
-6.3%
Not satisfactory
Return on total assets
Solidity
-29.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KJELSÅSVEIEN 168 DA?

No shareholders are registered for KJELSÅSVEIEN 168 DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KJELSÅSVEIEN 168 DA

What is the revenue of KJELSÅSVEIEN 168 DA?

KJELSÅSVEIEN 168 DA had revenue of NOK 2.0m in 2025.

Where is KJELSÅSVEIEN 168 DA based?

KJELSÅSVEIEN 168 DA 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 03.10.2026.

Report a problem

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