BIZTRAC BETA
Event catering activities

SPISEKROKEN EVJE AS

Org. no. 914260930 Limited company (AS) Evje Og Hornnes Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK 837,000
Equity NOK 1.2m
Incorporated 2014
Employees 8
Share capital NOK 30,000

SPISEKROKEN EVJE AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 914260930. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2014 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Catering og kafedrift, samt alt hva dermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK 837,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK 837,000
Equity
NOK 1.2m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns SPISEKROKEN EVJE AS?

HEIDI OSE-MADSEN
SPISEKROKEN EVJE AS
NOK 10.7m rev. · NOK 837,000 profit

SPISEKROKEN EVJE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPISEKROKEN EVJE AS

Who owns SPISEKROKEN EVJE AS?

HEIDI OSE-MADSEN is the largest registered owner, with 100.0%.

What is the revenue of SPISEKROKEN EVJE AS?

SPISEKROKEN EVJE AS had revenue of NOK 10.7m in 2024.

Who is the general manager of SPISEKROKEN EVJE AS?

Heidi Ose-Madsen is registered as general manager of SPISEKROKEN EVJE AS.

Where is SPISEKROKEN EVJE AS based?

SPISEKROKEN EVJE AS has its business address in Evje.

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.