BIZTRAC BETA
Business and other management consultancy activities

STERLING VON VALEN AS

Org. no. 914138213 Limited company (AS) Skjervøy Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 14,000
Incorporated 2014
Share capital NOK 30,000

STERLING VON VALEN AS is registered as a limited company in Skjervøy, Troms with organisation number 914138213. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester, foredragsvirksomhet, forretningsutvikling, deltagelse i andre selskaper og kjøp og salg av aksjer.”. 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
Operating profit
NOK 0
Equity
NOK 14,000
Est. value
NOK 22,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 STERLING VON VALEN AS?

RANDI ELISABETH VALEN
STERLING VON VALEN AS
NOK 0 rev. · NOK 0 profit

STERLING VON VALEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STERLING VON VALEN AS

Who owns STERLING VON VALEN AS?

RANDI ELISABETH VALEN is the largest registered owner, with 53.3%.

What is the revenue of STERLING VON VALEN AS?

STERLING VON VALEN AS had revenue of NOK 0 in 2025.

Who is the general manager of STERLING VON VALEN AS?

Harald Berby Karlsen Valen is registered as general manager of STERLING VON VALEN AS.

Where is STERLING VON VALEN AS based?

STERLING VON VALEN AS has its business address in Skjervøy.

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.