BIZTRAC BETA
Event catering activities

BIG CATERING OG EVENT AS

Org. no. 976493583 Limited company (AS) Grimstad Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 13.4m
Operating profit NOK 1.6m
Equity NOK 4.9m
Incorporated 1996
Employees 43
Share capital NOK 1.6m

BIG CATERING OG EVENT AS is registered as a limited company in Grimstad, Agder with organisation number 976493583. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 1996 and has 43 registered employees. Registered share capital is NOK 1.6m, divided into 1600 shares. The company's stated purpose is: “Catering, selskaper, kurs og konferanser, stevner og festivaler, sceneutleie, utleie fast eiendom og annen virksomhet som hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.4m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 13.4m
Operating profit
NOK 1.6m
Equity
NOK 4.9m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns BIG CATERING OG EVENT AS?

NORMISJON
BIG CATERING OG EVENT AS
NOK 13.4m rev. · NOK 1.6m profit

BIG CATERING OG EVENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIG CATERING OG EVENT AS

Who owns BIG CATERING OG EVENT AS?

NORMISJON is the largest registered owner, with 100.0%.

What is the revenue of BIG CATERING OG EVENT AS?

BIG CATERING OG EVENT AS had revenue of NOK 13.4m in 2024.

Who is the general manager of BIG CATERING OG EVENT AS?

Kåre Tommy Land is registered as general manager of BIG CATERING OG EVENT AS.

Where is BIG CATERING OG EVENT AS based?

BIG CATERING OG EVENT AS has its business address in Grimstad.

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.