BIZTRAC BETA
Wholesale of other machinery and equipment

KAFFE 378 AS

Org. no. 820615662 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 244,000
Operating profit NOK 181,000
Equity NOK 5.8m
Incorporated 2018
Share capital NOK 140,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KAFFE 378 AS is registered as a limited company in Bergen, Vestland with organisation number 820615662. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2018. Registered share capital is NOK 140,000, divided into 700 shares. The company's stated purpose is: “Investeringsvirksomhet og alt som hermed måtte stå i forbindelse, herunder deltakelse i andre foretak gjennom aksjeerverv.”. The most recent filed accounts, for the 2025 financial year, show NOK 244,000 in revenue and NOK 181,000 in operating profit.

Key figures · 2025

Revenue
NOK 244,000
Operating profit
NOK 181,000
Equity
NOK 5.8m
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
1.76
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
97.5%
Very good
Equity as a share of total capital

Who owns KAFFE 378 AS?

STEFFEN BROSVIK REIGSTAD
KAFFE 378 AS
NOK 244,000 rev. · NOK 181,000 profit

KAFFE 378 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KAFFE 378 AS own?

KAFFE 378 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KAFFE 378 AS

Who owns KAFFE 378 AS?

STEFFEN BROSVIK REIGSTAD is the largest registered owner, with 100.0%.

What is the revenue of KAFFE 378 AS?

KAFFE 378 AS had revenue of NOK 244,000 in 2025.

Where is KAFFE 378 AS based?

KAFFE 378 AS has its business address in Nyborg.

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.