biztrac. BETA
COMPANY REGISTER PROFILE
925504475 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Gambling and betting activities

VINNDRIFT AS

Org. no. 925504475 Limited company (AS) Lørenskog Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 2,000
Incorporated 2020
Share capital NOK 50,000

VINNDRIFT AS is registered as a limited company in Lørenskog, Akershus with organisation number 925504475. The business is classified under gambling and betting activities (NACE 92.000). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Å være operatør for spill til inntekt for samfunnsnyttige organisasjoner i Norge. Tillatelse til slike spill utstedes til organisasjonen av Lotteritilsynet, med selskapet som operatør.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK 0
▲ +100 %
Equity
NOK 2,000
▲ +0 %
Est. value
NOK 3,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
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 VINNDRIFT AS?

VINNDRIFT AS
NOK 0 rev. · NOK 0 profit

VINNDRIFT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VINNDRIFT AS

Who owns VINNDRIFT AS?

S S A INVEST AS is the largest registered owner, with 75.0%.

What is the revenue of VINNDRIFT AS?

VINNDRIFT AS had revenue of NOK 0 in 2025.

Who is the general manager of VINNDRIFT AS?

Steinar Sandvik is registered as general manager of VINNDRIFT AS.

Where is VINNDRIFT AS based?

VINNDRIFT AS has its business address in Rasta.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.