BIZTRAC BETA
Event catering activities

NOBEL CATERING & CONDITORI AS

Org. no. 931878409 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 23,000
Equity NOK 59,000
Incorporated 2023
Employees 20
Share capital NOK 30,000

NOBEL CATERING & CONDITORI AS is registered as a limited company in Bærum, Akershus with organisation number 931878409. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2023 and has 20 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen catering og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 23,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 23,000
Equity
NOK 59,000
Est. value
NOK 122,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NOBEL CATERING & CONDITORI AS?

OSLO LUNSJ AS
NOBEL CATERING & CONDITORI AS
NOK 1.3m rev. · NOK 23,000 profit

NOBEL CATERING & CONDITORI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOBEL CATERING & CONDITORI AS

Who owns NOBEL CATERING & CONDITORI AS?

OSLO LUNSJ AS is the largest registered owner, with 100.0%.

What is the revenue of NOBEL CATERING & CONDITORI AS?

NOBEL CATERING & CONDITORI AS had revenue of NOK 1.3m in 2024.

Where is NOBEL CATERING & CONDITORI AS based?

NOBEL CATERING & CONDITORI AS has its business address in Østerås.

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.