biztrac. BETA
COMPANY REGISTER PROFILE
924298006 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

GLOBUSBAR INVEST AS

Org. no. 924298006 Limited company (AS) Enebakk Incorporated 2019 Active
Operating profit NOK 0
Equity NOK 21,000
Incorporated 2019
Share capital NOK 30,000

GLOBUSBAR INVEST AS is registered as a limited company in Enebakk, Akershus with organisation number 924298006. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 21,000
▲ +0 %
Est. value
NOK 19,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GLOBUSBAR INVEST AS?

GLOBUSBAR INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GLOBUSBAR INVEST AS own?

GLOBUSBAR INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GLOBUSBAR INVEST AS

Who owns GLOBUSBAR INVEST AS?

Joachim Stanley Draget is the largest registered owner, with 50.0%.

Who is the general manager of GLOBUSBAR INVEST AS?

Joachim Stanley Draget is registered as general manager of GLOBUSBAR INVEST AS.

Where is GLOBUSBAR INVEST AS based?

GLOBUSBAR INVEST AS has its business address in Ytre Enebakk.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.