BIZTRAC BETA
Non-specialised wholesale of food, beverages and tobacco

KAFFELYKKEN AS

Org. no. 933911519 Limited company (AS) Larvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 961,000
Operating profit NOK 61,000
Equity NOK −14,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−14k kr).

KAFFELYKKEN AS is registered as a limited company in Larvik, Vestfold with organisation number 933911519. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Salg og utleie av utstyr og tilbehør til kontor og kantinedrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 961,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2025

Revenue
NOK 961,000
Operating profit
NOK 61,000
Equity
NOK −14,000
Est. value
NOK 323,000

Financial health · 2025

Liquidity
0.57
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.1%
Weak
Equity as a share of total capital

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

Who owns KAFFELYKKEN AS?

STINE STRETERE
KAFFELYKKEN AS
NOK 961,000 rev. · NOK 61,000 profit

KAFFELYKKEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KAFFELYKKEN AS

Who owns KAFFELYKKEN AS?

STINE STRETERE is the largest registered owner, with 33.3%.

What is the revenue of KAFFELYKKEN AS?

KAFFELYKKEN AS had revenue of NOK 961,000 in 2025.

Who is the general manager of KAFFELYKKEN AS?

Tom Bach is registered as general manager of KAFFELYKKEN AS.

Where is KAFFELYKKEN AS based?

KAFFELYKKEN AS has its business address in Larvik.

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.