BIZTRAC BETA
Rental and operating of own or leased real estate

GROOSEVEIEN 2 EIENDOM AS

Org. no. 995312824 Limited company (AS) Kristiansand Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 1.5m
Equity NOK 8.2m
Incorporated 2010
Share capital NOK 1.1m

GROOSEVEIEN 2 EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 995312824. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 1.1m, divided into 100 shares. The company's stated purpose is: “Å utvikle, eie og drifte fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 1.5m
Equity
NOK 8.2m
Est. value
NOK 7.8m

Financial health · 2024

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

Who owns GROOSEVEIEN 2 EIENDOM AS?

NG EIENDOM AGDER AS
GROOSEVEIEN 2 EIENDOM AS
NOK 2.7m rev. · NOK 1.5m profit

GROOSEVEIEN 2 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GROOSEVEIEN 2 EIENDOM AS er morselskap for 249 datterselskaper:

Frequently asked questions about GROOSEVEIEN 2 EIENDOM AS

Who owns GROOSEVEIEN 2 EIENDOM AS?

NG EIENDOM AGDER AS is the largest registered owner, with 100.0%.

What is the revenue of GROOSEVEIEN 2 EIENDOM AS?

GROOSEVEIEN 2 EIENDOM AS had revenue of NOK 2.7m in 2024.

Who is the general manager of GROOSEVEIEN 2 EIENDOM AS?

Christian Thomassen is registered as general manager of GROOSEVEIEN 2 EIENDOM AS.

Where is GROOSEVEIEN 2 EIENDOM AS based?

GROOSEVEIEN 2 EIENDOM 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.