BIZTRAC BETA
Event catering activities

GRILLO CATERING AS

Org. no. 997077903 Limited company (AS) Sortland Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 77,000
Equity NOK −606,000
Incorporated 2011
Share capital NOK 160,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−606k kr).

GRILLO CATERING AS is registered as a limited company in Sortland, Nordland with organisation number 997077903. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2011. Registered share capital is NOK 160,000, divided into 1600 shares. The company's stated purpose is: “Catering og tjenester som faller naturlig inn under dette, herunder delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 77,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 77,000
Equity
NOK −606,000
Est. value
NOK 348,000

Financial health · 2024

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

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

Who owns GRILLO CATERING AS?

TORE WILLASSEN
GRILLO CATERING AS
NOK 1.3m rev. · NOK 77,000 profit

GRILLO CATERING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRILLO CATERING AS

Who owns GRILLO CATERING AS?

TORE WILLASSEN is the largest registered owner, with 71.9%.

What is the revenue of GRILLO CATERING AS?

GRILLO CATERING AS had revenue of NOK 1.3m in 2024.

Who is the general manager of GRILLO CATERING AS?

Tore Willassen is registered as general manager of GRILLO CATERING AS.

Where is GRILLO CATERING AS based?

GRILLO CATERING AS has its business address in Sortland.

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.