BIZTRAC BETA
Rental and operating of own or leased real estate

ELVEGATA 2A AS

Org. no. 999214053 Limited company (AS) Kristiansand Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 9.3m
Equity NOK 37.7m
Incorporated 2012
Share capital NOK 88,000

Signals

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

ELVEGATA 2A AS is registered as a limited company in Kristiansand, Agder with organisation number 999214053. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 88,000, divided into 57 shares. The company's stated purpose is: “Utleie av fast eiendom, kjøp og salg av fast eiendom, samt investering i aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 9.3m in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 9.3m
Equity
NOK 37.7m
Est. value
NOK 45.1m

Financial health · 2024

Liquidity
8.85
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.1%
Very good
Equity as a share of total capital

Who owns ELVEGATA 2A AS?

IVAR MJÅLAND EIENDOM AS
ELVEGATA 2A AS
NOK 4.8m rev. · NOK 9.3m profit

ELVEGATA 2A AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELVEGATA 2A AS

Who owns ELVEGATA 2A AS?

IVAR MJÅLAND EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ELVEGATA 2A AS?

ELVEGATA 2A AS had revenue of NOK 4.8m in 2024.

Who is the general manager of ELVEGATA 2A AS?

Tore Nielsen is registered as general manager of ELVEGATA 2A AS.

Where is ELVEGATA 2A AS based?

ELVEGATA 2A AS has its business address in Kristiansand S.

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.