BIZTRAC BETA
Retail sale of other food

KAFFE & KRYDDER AS

Org. no. 923240365 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK −44,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−44k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

KAFFE & KRYDDER AS is registered as a limited company in Oslo, Oslo with organisation number 923240365. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Netthandel for kaffe og krydder og lignende.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK −44,000

Financial health · 2024

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

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

Who owns KAFFE & KRYDDER AS?

BJØRN SALVESEN BORGLAND
KAFFE & KRYDDER AS
NOK 0 rev. · NOK −11,000 profit

KAFFE & KRYDDER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAFFE & KRYDDER AS

Who owns KAFFE & KRYDDER AS?

BJØRN SALVESEN BORGLAND is the largest registered owner, with 100.0%.

What is the revenue of KAFFE & KRYDDER AS?

KAFFE & KRYDDER AS had revenue of NOK 0 in 2024.

Who is the general manager of KAFFE & KRYDDER AS?

Bjørn Salvesen Borgland is registered as general manager of KAFFE & KRYDDER AS.

Where is KAFFE & KRYDDER AS based?

KAFFE & KRYDDER AS has its business address in Oslo.

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.