BIZTRAC BETA
Development of building projects

AMALIENBORG BRYGGE 2 AS

Org. no. 930481661 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 197.9m
Operating profit NOK 33.0m
Equity NOK 59.7m
Incorporated 2022
Share capital NOK 83,000

Signals

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

AMALIENBORG BRYGGE 2 AS is registered as a limited company in Kristiansand, Agder with organisation number 930481661. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 83,000, divided into 1000 shares. The company's stated purpose is: “Utvikling, utbygging, kjøp, salg og utleie av eiendom, samt drift av fast eiendom og alt som herved står i forbindelse, herunder å delta i selskaper med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 197.9m in revenue and NOK 33.0m in operating profit.

Key figures · 2024

Revenue
NOK 197.9m
Operating profit
NOK 33.0m
Equity
NOK 59.7m
Est. value
NOK 121.0m

Financial health · 2024

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

Who owns AMALIENBORG BRYGGE 2 AS?

SKEIE EIENDOM AS
AMALIENBORG BRYGGE 2 AS
NOK 197.9m rev. · NOK 33.0m profit

AMALIENBORG BRYGGE 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMALIENBORG BRYGGE 2 AS

Who owns AMALIENBORG BRYGGE 2 AS?

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

What is the revenue of AMALIENBORG BRYGGE 2 AS?

AMALIENBORG BRYGGE 2 AS had revenue of NOK 197.9m in 2024.

Where is AMALIENBORG BRYGGE 2 AS based?

AMALIENBORG BRYGGE 2 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.