BIZTRAC BETA
Contract catering service activities and other food service activities

ERUCA AS

Org. no. 921540914 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −52,000
Equity NOK 19.6m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−52k kr).

ERUCA AS is registered as a limited company in Stavanger, Rogaland with organisation number 921540914. The business is classified under contract catering service activities and other food service activities (NACE 56.220). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøpe og selge aksjer og andre verdipapirer, herunder å delta i andre selskaper med lignende virksomhet. Selskapet kan delta i og inneha eierandeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −52,000
Equity
NOK 19.6m
Est. value
NOK 86.1m

Financial health · 2025

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

Who owns ERUCA AS?

STEFFEN GJESSEN KYLEVIK
ERUCA AS
NOK 0 rev. · NOK −52,000 profit

ERUCA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ERUCA AS own?

ERUCA AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about ERUCA AS

Who owns ERUCA AS?

STEFFEN GJESSEN KYLEVIK is the largest registered owner, with 50.0%.

What is the revenue of ERUCA AS?

ERUCA AS had revenue of NOK 0 in 2025.

Where is ERUCA AS based?

ERUCA AS has its business address in Stavanger.

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.