BIZTRAC BETA
Other captive investment companies

VELIPE AS

Org. no. 918331484 Limited company (AS) Øygarden Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 919,000
Operating profit NOK 867,000
Equity NOK 13.7m
Incorporated 2016
Share capital NOK 30,000

VELIPE AS is registered as a limited company in Øygarden, Vestland with organisation number 918331484. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 101 shares. The company's stated purpose is: “Å skaffe aksjeeierne utbytte ved konsulentvirksomhet, undervisning, investering i andre selskaper og hva dermed står forbindelse, investering i eiendom, garantistillelse, handel og i særskilte tilfeller yte lån.”. The most recent filed accounts, for the 2025 financial year, show NOK 919,000 in revenue and NOK 867,000 in operating profit.

Key figures · 2025

Revenue
NOK 919,000
Operating profit
NOK 867,000
Equity
NOK 13.7m
Est. value
NOK 10.1m

Financial health · 2025

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

Who owns VELIPE AS?

PER-ATLE TELLNES
VELIPE AS
NOK 919,000 rev. · NOK 867,000 profit

VELIPE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VELIPE AS own?

VELIPE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VELIPE AS

Who owns VELIPE AS?

PER-ATLE TELLNES is the largest registered owner, with 100.0%.

What is the revenue of VELIPE AS?

VELIPE AS had revenue of NOK 919,000 in 2025.

Who is the general manager of VELIPE AS?

Per-Atle Tellnes is registered as general manager of VELIPE AS.

Where is VELIPE AS based?

VELIPE AS has its business address in Skogsvåg.

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.