BIZTRAC BETA
Restaurant activities

CATERING SERVICE AS

Org. no. 934455126 Limited company (AS) Moss Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 695,000
Operating profit NOK −50,000
Equity NOK −840,000
Incorporated 1984
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−840k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−50k kr).

CATERING SERVICE AS is registered as a limited company in Moss, Østfold with organisation number 934455126. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1984. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Drive innenfor serveringsvirksomhet, administrative tjenester, konsulent tjenester og investeringsvirksomhet, kjøp og salg av aksjer og selskapsandeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 695,000 in revenue and NOK −50,000 in operating profit.

Key figures · 2024

Revenue
NOK 695,000
Operating profit
NOK −50,000
Equity
NOK −840,000

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-263.6%
Weak
Equity as a share of total capital

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

Who owns CATERING SERVICE AS?

SVEIN EGIL SOLSKJÆR
CATERING SERVICE AS
NOK 695,000 rev. · NOK −50,000 profit

CATERING SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CATERING SERVICE AS

Who owns CATERING SERVICE AS?

SVEIN EGIL SOLSKJÆR is the largest registered owner, with 100.0%.

What is the revenue of CATERING SERVICE AS?

CATERING SERVICE AS had revenue of NOK 695,000 in 2024.

Where is CATERING SERVICE AS based?

CATERING SERVICE AS has its business address in Moss.

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.