BIZTRAC BETA
Processing of tea and coffee

ELLINGSEN KAFFEBRENNERI AS

Org. no. 920519423 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 7.7m
Operating profit NOK 642,000
Equity NOK 331,000
Incorporated 2018
Employees 9
Share capital NOK 100,000

ELLINGSEN KAFFEBRENNERI AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920519423. The business is classified under processing of tea and coffee (NACE 10.830). The company was incorporated in 2018 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Innkjøp, brenning og salg av kaffe, og aktiviteter beslektet med eller knyttet til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.7m in revenue and NOK 642,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.7m
Operating profit
NOK 642,000
Equity
NOK 331,000
Est. value
NOK 2.6m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.6%
Good
Equity as a share of total capital

Who owns ELLINGSEN KAFFEBRENNERI AS?

MIT HOLDING AS
ELLINGSEN KAFFEBRENNERI AS
NOK 7.7m rev. · NOK 642,000 profit

ELLINGSEN KAFFEBRENNERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELLINGSEN KAFFEBRENNERI AS

Who owns ELLINGSEN KAFFEBRENNERI AS?

MIT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ELLINGSEN KAFFEBRENNERI AS?

ELLINGSEN KAFFEBRENNERI AS had revenue of NOK 7.7m in 2024.

Who is the general manager of ELLINGSEN KAFFEBRENNERI AS?

Idar André Ellingsen is registered as general manager of ELLINGSEN KAFFEBRENNERI AS.

Where is ELLINGSEN KAFFEBRENNERI AS based?

ELLINGSEN KAFFEBRENNERI AS has its business address in Tiller.

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.