BIZTRAC BETA
Wholesale of other machinery and equipment

KAFFEBRYGGERIET AS

Org. no. 890742262 Limited company (AS) Lillestrøm Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 94.6m
Operating profit NOK 13.9m
Equity NOK 36.8m
Incorporated 2006
Employees 36
Share capital NOK 340,000

KAFFEBRYGGERIET AS is registered as a limited company in Lillestrøm, Akershus with organisation number 890742262. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2006 and has 36 registered employees. Registered share capital is NOK 340,000, divided into 340 shares. The company's stated purpose is: “Salg og utleie av varer og tjenester innen kaffe og tilhørende produkter, samt det som naturlig står i forbindelse med dette, herunder eierskap i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 94.6m in revenue and NOK 13.9m in operating profit.

Key figures · 2024

Revenue
NOK 94.6m
Operating profit
NOK 13.9m
Equity
NOK 36.8m
Est. value
NOK 67.2m

Financial health · 2024

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

Who owns KAFFEBRYGGERIET AS?

MIKO KOFFIE NV
KAFFEBRYGGERIET AS
NOK 94.6m rev. · NOK 13.9m profit

KAFFEBRYGGERIET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAFFEBRYGGERIET AS

Who owns KAFFEBRYGGERIET AS?

MIKO KOFFIE NV is the largest registered owner, with 100.0%.

What is the revenue of KAFFEBRYGGERIET AS?

KAFFEBRYGGERIET AS had revenue of NOK 94.6m in 2024.

Who is the general manager of KAFFEBRYGGERIET AS?

Bård Aune is registered as general manager of KAFFEBRYGGERIET AS.

Where is KAFFEBRYGGERIET AS based?

KAFFEBRYGGERIET AS has its business address in Kjeller.

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.