BIZTRAC BETA
Uoppgitt

VAPEQUEEN AS

Org. no. 925194522 Limited company (AS) Lindesnes Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 128,000
Operating profit NOK 41,000
Equity NOK 3.0m
Incorporated 2020
Share capital NOK 30,000

VAPEQUEEN AS is registered as a limited company in Lindesnes, Agder with organisation number 925194522. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 15 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, investering i fast eiendom og verdipapirer, herunder lånefinansierte investeringer med verdipapirer og valuta og annet 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 2024 financial year, show NOK 128,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2024

Revenue
NOK 128,000
Operating profit
NOK 41,000
Equity
NOK 3.0m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns VAPEQUEEN AS?

RUTH-ELIN BERGUM
VAPEQUEEN AS
NOK 128,000 rev. · NOK 41,000 profit

VAPEQUEEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VAPEQUEEN AS own?

VAPEQUEEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VAPEQUEEN AS

Who owns VAPEQUEEN AS?

RUTH-ELIN BERGUM is the largest registered owner, with 100.0%.

What is the revenue of VAPEQUEEN AS?

VAPEQUEEN AS had revenue of NOK 128,000 in 2024.

Where is VAPEQUEEN AS based?

VAPEQUEEN AS has its business address in Marnardal.

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.