biztrac. BETA
COMPANY REGISTER PROFILE
985228221 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

PLAN V AS

Org. no. 985228221 Limited company (AS) Skien Incorporated 2002 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 100,000
Incorporated 2002
Share capital NOK 100,000

PLAN V AS is registered as a limited company in Skien, Telemark with organisation number 985228221. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Økonomitjenester. Videre kan selskapet drive innenfor forskjellig typer bedriftsrådgivning samt å være konsulenter for andre virksomheter. Det skal være anledning til å eie aksjer og andeler i andre selskaper, samt hva herved naturlig står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: TEN-FOUR CLOTHING AS, VECTOR PLAN AS

Key figures · 2025

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

Financial health · 2025

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

Who owns PLAN V AS?

LINDE INVEST LTD. GB
PLAN V AS
NOK 0 rev. · NOK 0 profit

PLAN V AS has 1 registered shareholder:

  • LINDE INVEST LTD. 100.0%
All shareholders and roles →

Frequently asked questions about PLAN V AS

Who owns PLAN V AS?

LINDE INVEST LTD. is the largest registered owner, with 100.0%.

What is the revenue of PLAN V AS?

PLAN V AS had revenue of NOK 0 in 2025.

Where is PLAN V AS based?

PLAN V AS has its business address in Skien.

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.