biztrac. BETA
COMPANY REGISTER PROFILE
997538617 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠TØNSBERG KAFFE AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Restaurant activities

TØNSBERG KAFFE AS

Org. no. 997538617 Limited company (AS) Tønsberg Incorporated 2011 In liquidation
Revenue 2025 NOK 800
Operating profit NOK −76,000
Equity NOK 49,000
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

TØNSBERG KAFFE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 997538617. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av restauranter og alt som står i forhold til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 800 in revenue and NOK −76,000 in operating profit.

Key figures · 2025

Revenue
NOK 800
▼ −100 %
Operating profit
NOK −76,000
▼ −1019 %
Equity
NOK 49,000
▼ −61 %

Financial health · 2025

Liquidity
14.07
Very good
Current assets ÷ current liabilities
Profitability
-25.7%
Not satisfactory
Return on total assets
Solidity
92.9%
Weak
Equity as a share of total capital

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

Who owns TØNSBERG KAFFE AS?

TØNSBERG KAFFE AS
NOK 800 rev. · NOK −76,000 profit

TØNSBERG KAFFE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TØNSBERG KAFFE AS

Who owns TØNSBERG KAFFE AS?

Kim Johnsgård is the largest registered owner, with 51.0%.

What is the revenue of TØNSBERG KAFFE AS?

TØNSBERG KAFFE AS had revenue of NOK 800 in 2025.

Where is TØNSBERG KAFFE AS based?

TØNSBERG KAFFE 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 03.10.2026.

Report a problem

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