BIZTRAC BETA
Event catering activities

MAXI CATERING AS

Org. no. 915418309 Limited company (AS) Kristiansand Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 31.7m
Operating profit NOK 678,000
Equity NOK 100,000
Incorporated 2015
Employees 17
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MAXI CATERING AS is registered as a limited company in Kristiansand, Agder with organisation number 915418309. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2015 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive med catering og det som naturlig hører sammen med dette. ”. The most recent filed accounts, for the 2024 financial year, show NOK 31.7m in revenue and NOK 678,000 in operating profit.

Key figures · 2024

Revenue
NOK 31.7m
Operating profit
NOK 678,000
Equity
NOK 100,000
Est. value
NOK 2.6m

Financial health · 2024

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.2%
Not satisfactory
Equity as a share of total capital

Who owns MAXI CATERING AS?

GORINES AS
MAXI CATERING AS
NOK 31.7m rev. · NOK 678,000 profit

MAXI CATERING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAXI CATERING AS own?

MAXI CATERING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MAXI CATERING AS

Who owns MAXI CATERING AS?

GORINES AS is the largest registered owner, with 100.0%.

What is the revenue of MAXI CATERING AS?

MAXI CATERING AS had revenue of NOK 31.7m in 2024.

Where is MAXI CATERING AS based?

MAXI CATERING AS has its business address in Kristiansand 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.