BIZTRAC BETA
Event catering activities

SAGENE SYSLER AS

Org. no. 933111407 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 63,000
Operating profit NOK −166
Equity NOK 27,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−166 kr).

SAGENE SYSLER AS is registered as a limited company in Oslo, Oslo with organisation number 933111407. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Formidling av mat- og håndverkstradisjoner, småproduksjon, tjenesteyting og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 63,000 in revenue and NOK −166 in operating profit.

Key figures · 2025

Revenue
NOK 63,000
Operating profit
NOK −166
Equity
NOK 27,000
Est. value
NOK 58,000

Financial health · 2025

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

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

Who owns SAGENE SYSLER AS?

HANS HÅVARD KVISLE
SAGENE SYSLER AS
NOK 63,000 rev. · NOK −166 profit

SAGENE SYSLER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAGENE SYSLER AS

Who owns SAGENE SYSLER AS?

HANS HÅVARD KVISLE is the largest registered owner, with 50.0%.

What is the revenue of SAGENE SYSLER AS?

SAGENE SYSLER AS had revenue of NOK 63,000 in 2025.

Who is the general manager of SAGENE SYSLER AS?

Hans Håvard Kvisle is registered as general manager of SAGENE SYSLER AS.

Where is SAGENE SYSLER AS based?

SAGENE SYSLER AS has its business address in Oslo.

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.