BIZTRAC BETA
Computer programming activities

VAPARA AS

Org. no. 914379857 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 171,000
Operating profit NOK 44,000
Equity NOK 81,000
Incorporated 2014
Share capital NOK 30,000

VAPARA AS is registered as a limited company in Oslo, Oslo with organisation number 914379857. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling av digitale konsepter med dertilhørende salg av varer og tjenester og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 171,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 171,000
Operating profit
NOK 44,000
Equity
NOK 81,000
Est. value
NOK 242,000

Financial health · 2025

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

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

Who owns VAPARA AS?

STÅLE EIKERI
VAPARA AS
NOK 171,000 rev. · NOK 44,000 profit

VAPARA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VAPARA AS own?

VAPARA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VAPARA AS

Who owns VAPARA AS?

STÅLE EIKERI is the largest registered owner, with 100.0%.

What is the revenue of VAPARA AS?

VAPARA AS had revenue of NOK 171,000 in 2025.

Where is VAPARA AS based?

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