biztrac. BETA
COMPANY REGISTER PROFILE
989195050 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

WENAAS HOLDING AS

Org. no. 989195050 Limited company (AS) Rauma Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −89,000
Equity NOK 74.1m
Incorporated 2005
Share capital NOK 148,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−89k kr).
  • Nylig endring 2026-09-24 Aksjekapital registrert 2026-09-24.

WENAAS HOLDING AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 989195050. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 148,000, divided into 1252 shares. The company's stated purpose is: “Erverv, utvikling og forvaltning av faste eiendommer, samt investering i aksjer, obligasjoner og andre verdipapirer, samt annen økonomisk virksomhet, herunder også å delta i andre selskaper med lignende virksomhet.”.

Former names: LARNI INVEST AS, WELAR AS

Key figures · 2025

Operating profit
NOK −89,000
▼ −4 %
Equity
NOK 74.1m
▲ +72 %
Est. value
NOK 152.2m

Financial health · 2025

Liquidity
1.76
Good
Current assets ÷ current liabilities
Profitability
22.9%
Very good
Return on total assets
Solidity
46.3%
Very good
Equity as a share of total capital

Who owns WENAAS HOLDING AS?

WENAAS HOLDING AS
· NOK −89,000 profit

WENAAS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WENAAS HOLDING AS own?

WENAAS HOLDING AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about WENAAS HOLDING AS

Who owns WENAAS HOLDING AS?

Lars Wenaas is the largest registered owner, with 100.0%.

Where is WENAAS HOLDING AS based?

WENAAS HOLDING AS has its business address in Måndalen.

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.