BIZTRAC BETA
Other captive investment companies

BETA INVEST AS

Org. no. 980394026 Limited company (AS) Namsos Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −39,000
Equity NOK 157,000
Incorporated 1998
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−39k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BETA INVEST AS is registered as a limited company in Namsos, Trøndelag with organisation number 980394026. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Industri, handel, ervervelse- forvaltning og omsetning av fast eiendom, løsøre og verdipapirer, konsulent- og agentvirksomhet, samt ved aksjer eller på annen måte delta i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −39,000
Equity
NOK 157,000
Est. value
NOK 11.7m

Financial health · 2024

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.7%
Weak
Equity as a share of total capital

Who owns BETA INVEST AS?

BPAS INVEST AS
BETA INVEST AS
NOK 0 rev. · NOK −39,000 profit

BETA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BETA INVEST AS

Who owns BETA INVEST AS?

BPAS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BETA INVEST AS?

BETA INVEST AS had revenue of NOK 0 in 2024.

Where is BETA INVEST AS based?

BETA INVEST AS has its business address in Namsos.

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.