BIZTRAC BETA
Event catering activities

CATERING & CREW AS

Org. no. 984590938 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 15.4m
Operating profit NOK 227,000
Equity NOK 642,000
Incorporated 2002
Employees 19
Share capital NOK 100,000

CATERING & CREW AS is registered as a limited company in Oslo, Oslo with organisation number 984590938. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2002 and has 19 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av mat m.v. og herunder beslektede produkter som naturlig hører sammen med dette, samt frakt ut og inn av dette. Videre skal selskapet kunne erverve fast eiendom og stå for driften av slike. ”. The most recent filed accounts, for the 2025 financial year, show NOK 15.4m in revenue and NOK 227,000 in operating profit.

Key figures · 2025

Revenue
NOK 15.4m
Operating profit
NOK 227,000
Equity
NOK 642,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns CATERING & CREW AS?

JARLE KOPPERUD
CATERING & CREW AS
NOK 15.4m rev. · NOK 227,000 profit

CATERING & CREW AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CATERING & CREW AS

Who owns CATERING & CREW AS?

JARLE KOPPERUD is the largest registered owner, with 50.0%.

What is the revenue of CATERING & CREW AS?

CATERING & CREW AS had revenue of NOK 15.4m in 2025.

Who is the general manager of CATERING & CREW AS?

Jarle Kopperud is registered as general manager of CATERING & CREW AS.

Where is CATERING & CREW AS based?

CATERING & CREW AS has its business address in Oslo.

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.