BIZTRAC BETA
COMPANY REGISTER PROFILE
834094762 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

ARLA AS

Org. no. 834094762 Limited company (AS) Haugesund Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

ARLA AS is registered as a limited company in Haugesund, Rogaland with organisation number 834094762. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av eiendommer og utleie av eiendommer og annet som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −2,000
▼ −37167 %
Equity
NOK 24,000
▼ −2 %
Est. value
NOK 22,000

Financial health · 2025

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

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

Who owns ARLA AS?

ARLA AS
· NOK −2,000 profit

ARLA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARLA AS

Who owns ARLA AS?

LAILA ARNESEN is the largest registered owner, with 100.0%.

Where is ARLA AS based?

ARLA AS has its business address in Haugesund.

Property

Business address Kon-Tikivegen 15C, 5519 Haugesund
Cadastral unit 1106-28/455/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.