BIZTRAC BETA
Rental and operating of own or leased real estate

BETA EIENDOM AS

Org. no. 884698782 Limited company (AS) Namsos Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 554,000
Equity NOK 649,000
Incorporated 2002
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BETA EIENDOM AS is registered as a limited company in Namsos, Trøndelag with organisation number 884698782. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Utleie av eiendom, samt ved aksjer eller på annen måte delta i annen forretningsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 554,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 554,000
Equity
NOK 649,000
Est. value
NOK 1.2m

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.7%
Weak
Equity as a share of total capital

Who owns BETA EIENDOM AS?

BPAS INVEST AS
BETA EIENDOM AS
NOK 1.2m rev. · NOK 554,000 profit

BETA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BETA EIENDOM AS own?

BETA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BETA EIENDOM AS

Who owns BETA EIENDOM AS?

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

What is the revenue of BETA EIENDOM AS?

BETA EIENDOM AS had revenue of NOK 1.2m in 2024.

Where is BETA EIENDOM AS based?

BETA EIENDOM 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.