BIZTRAC BETA
Business and other management consultancy activities

VINCERE-NOS AS

Org. no. 826425962 Limited company (AS) Leka Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 9,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

VINCERE-NOS AS is registered as a limited company in Leka, Trøndelag with organisation number 826425962. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 3 shares. The company's stated purpose is: “Rådgivingstjeneste, forlagsvirksomhet, investeringsvirksomhet, og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 9,000
Est. value
NOK 15,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VINCERE-NOS AS?

HELGE THORSEN
VINCERE-NOS AS
NOK 0 rev. · NOK −2,000 profit

VINCERE-NOS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINCERE-NOS AS

Who owns VINCERE-NOS AS?

HELGE THORSEN is the largest registered owner, with 100.0%.

What is the revenue of VINCERE-NOS AS?

VINCERE-NOS AS had revenue of NOK 0 in 2025.

Where is VINCERE-NOS AS based?

VINCERE-NOS AS has its business address in Leka.

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.