BIZTRAC BETA
Computer programming activities

VIDERE PLAN AS

Org. no. 935969026 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

VIDERE PLAN AS is registered as a limited company in Oslo, Oslo with organisation number 935969026. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen programvare, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 23,000
Est. value
NOK 42,000

Financial health · 2025

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 VIDERE PLAN AS?

BIOMETRIX AS
VIDERE PLAN AS
NOK 0 rev. · NOK −7,000 profit

VIDERE PLAN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIDERE PLAN AS

Who owns VIDERE PLAN AS?

BIOMETRIX AS is the largest registered owner, with 66.7%.

What is the revenue of VIDERE PLAN AS?

VIDERE PLAN AS had revenue of NOK 0 in 2025.

Who is the general manager of VIDERE PLAN AS?

Jan Victor Qian is registered as general manager of VIDERE PLAN AS.

Where is VIDERE PLAN AS based?

VIDERE PLAN 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.