biztrac. BETA
COMPANY REGISTER PROFILE
999303579 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

VENEKA AS

Org. no. 999303579 Limited company (AS) Molde Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK 140,000
Incorporated 2012
Share capital NOK 100,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-07-21 Adresseendring registrert 2026-07-21.

VENEKA AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 999303579. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Holdingselskap ved aksjeinvestering og eiendomsinvesteringer, samt annen virksomhet som naturlig hører sammen med dette.”.

Former names: SPORTSLAGERET 3S AS, I-SPORT SUNNDALSØRA AS

Key figures · 2025

Operating profit
NOK −25,000
▲ +50 %
Equity
NOK 140,000
▼ −16 %
Est. value
NOK 164,000

Financial health · 2025

Liquidity
1.70
Good
Current assets ÷ current liabilities
Profitability
-8.9%
Not satisfactory
Return on total assets
Solidity
41.1%
Very good
Equity as a share of total capital

Who owns VENEKA AS?

VENEKA AS
· NOK −25,000 profit

VENEKA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VENEKA AS er morselskap for 5 datterselskaper:

Frequently asked questions about VENEKA AS

Who owns VENEKA AS?

3S HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of VENEKA AS?

Yendami Petit Sjøvik is registered as general manager of VENEKA AS.

Where is VENEKA AS based?

VENEKA AS has its business address in Midsund.

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.