BIZTRAC BETA
Event catering activities

FORUS EVENT AS

Org. no. 936157114 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 56,000
Operating profit NOK −14,000
Equity NOK 279,000
Incorporated 2025
Employees 21
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-12.

FORUS EVENT AS is registered as a limited company in Stavanger, Rogaland with organisation number 936157114. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2025 and has 21 registered employees. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Drift av restaurant, bar, cateringvirksomhet, samt opplevelses- arrangementer.”. The most recent filed accounts, for the 2025 financial year, show NOK 56,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 56,000
Operating profit
NOK −14,000
Equity
NOK 279,000
Est. value
NOK 180,000

Financial health · 2025

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

Who owns FORUS EVENT AS?

KJETIL HOVE
FORUS EVENT AS
NOK 56,000 rev. · NOK −14,000 profit

FORUS EVENT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FORUS EVENT AS

Who owns FORUS EVENT AS?

KJETIL HOVE is the largest registered owner, with 33.3%.

What is the revenue of FORUS EVENT AS?

FORUS EVENT AS had revenue of NOK 56,000 in 2025.

Who is the general manager of FORUS EVENT AS?

Kjetil Hove is registered as general manager of FORUS EVENT AS.

Where is FORUS EVENT AS based?

FORUS EVENT AS has its business address in Stavanger.

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.