BIZTRAC BETA
Rental and operating of own or leased real estate

GRØNLAND 68 AS

Org. no. 997403541 Limited company (AS) Drammen Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 3.4m
Equity NOK 924,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

GRØNLAND 68 AS is registered as a limited company in Drammen, Buskerud with organisation number 997403541. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 3.4m in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 3.4m
Equity
NOK 924,000
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns GRØNLAND 68 AS?

UNION BRYGGE EIENDOM AS
GRØNLAND 68 AS
NOK 4.9m rev. · NOK 3.4m profit

GRØNLAND 68 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRØNLAND 68 AS

Who owns GRØNLAND 68 AS?

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

What is the revenue of GRØNLAND 68 AS?

GRØNLAND 68 AS had revenue of NOK 4.9m in 2024.

Who is the general manager of GRØNLAND 68 AS?

Jan Eirik Berntsen is registered as general manager of GRØNLAND 68 AS.

Where is GRØNLAND 68 AS based?

GRØNLAND 68 AS has its business address in Drammen.

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.