BIZTRAC BETA
Development of building projects

BLØDEKJÆRVEIEN 18 AS

Org. no. 912531082 Limited company (AS) Arendal Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 629,000
Operating profit NOK 277,000
Equity NOK 706,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

BLØDEKJÆRVEIEN 18 AS is registered as a limited company in Arendal, Agder with organisation number 912531082. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie, kjøp, salg, utleie og utvikling av fast eiendom og alt hva som hermed står i forbindelse, samt å delta i andre virksomheter i samme eller lignende bransjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 629,000 in revenue and NOK 277,000 in operating profit.

Key figures · 2024

Revenue
NOK 629,000
Operating profit
NOK 277,000
Equity
NOK 706,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.7%
Good
Equity as a share of total capital

Who owns BLØDEKJÆRVEIEN 18 AS?

ABC HALVORSEN EIENDOM AS
BLØDEKJÆRVEIEN 18 AS
NOK 629,000 rev. · NOK 277,000 profit

BLØDEKJÆRVEIEN 18 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLØDEKJÆRVEIEN 18 AS

Who owns BLØDEKJÆRVEIEN 18 AS?

ABC HALVORSEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BLØDEKJÆRVEIEN 18 AS?

BLØDEKJÆRVEIEN 18 AS had revenue of NOK 629,000 in 2024.

Where is BLØDEKJÆRVEIEN 18 AS based?

BLØDEKJÆRVEIEN 18 AS has its business address in Kongshavn.

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.