BIZTRAC BETA
COMPANY REGISTER PROFILE
934195485 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

KVITTEN AS

Org. no. 934195485 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK 109,000
Incorporated 2024
Share capital NOK 124,000

Signals

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

KVITTEN AS is registered as a limited company in Oslo, Oslo with organisation number 934195485. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 124,000, divided into 1031 shares. The company's stated purpose is: “Utvikling og drift av digitale løsninger som reduserer bruk av papir og skaper merverdi gjennom markedsføringskanaler, inkludert salg av teknologi, tjenester og produkter relatert til digitale løsninger.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Former names: KVITTLY AS

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 109,000
Est. value
NOK 197,000

Financial health · 2024

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

Who owns KVITTEN AS?

SANDER LUND SØNSTERUD
KVITTEN AS
NOK 0 rev. · NOK −11,000 profit

KVITTEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVITTEN AS

Who owns KVITTEN AS?

SANDER LUND SØNSTERUD is the largest registered owner, with 32.4%.

What is the revenue of KVITTEN AS?

KVITTEN AS had revenue of NOK 0 in 2024.

Where is KVITTEN AS based?

KVITTEN 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.