BIZTRAC BETA
Computer consultancy and computer facilities management activities

SAGA PAYMENTS AS

Org. no. 934751183 Limited company (AS) Gjerdrum Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

SAGA PAYMENTS AS is registered as a limited company in Gjerdrum, Akershus with organisation number 934751183. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 150,000, divided into 500000 shares. The company's stated purpose is: “Drive betalingsformidlingstjenester gjennom samarbeid med lisensierte partnere, samt investere i verdipapirer og finansielle instrumenter. Videre kan selskapet yte rådgivning og tjenester knyttet til finans, teknologi og investeringer, samt drive annen virksomhet som naturlig hører sammen med dette.”.

Key figures · 2024

Operating profit
NOK −6,000
Equity
NOK 24,000
Est. value
NOK 44,000

Financial health · 2024

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

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

Who owns SAGA PAYMENTS AS?

TORBJØRN KALVENES
SAGA PAYMENTS AS
· NOK −6,000 profit

SAGA PAYMENTS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAGA PAYMENTS AS

Who owns SAGA PAYMENTS AS?

TORBJØRN KALVENES is the largest registered owner, with 25.0%.

Who is the general manager of SAGA PAYMENTS AS?

Kristoffer Henriksen Aga is registered as general manager of SAGA PAYMENTS AS.

Where is SAGA PAYMENTS AS based?

SAGA PAYMENTS AS has its business address in Gjerdrum.

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.