BIZTRAC BETA
Rental and operating of own or leased real estate

GLOBALTEK EIENDOM AS

Org. no. 989467816 Limited company (AS) Melhus Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 845,000
Operating profit NOK 177,000
Equity NOK 1.6m
Incorporated 2006
Share capital NOK 615,000

GLOBALTEK EIENDOM AS is registered as a limited company in Melhus, Trøndelag with organisation number 989467816. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 615,000, divided into 615 shares. The company's stated purpose is: “Eiendomsselskap med kjøp og utleie av eiendom og annen virksomhet som naturlig hører med under eiendomsutvikling, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 845,000 in revenue and NOK 177,000 in operating profit.

Key figures · 2024

Revenue
NOK 845,000
Operating profit
NOK 177,000
Equity
NOK 1.6m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns GLOBALTEK EIENDOM AS?

RIAN HOLDING AS
GLOBALTEK EIENDOM AS
NOK 845,000 rev. · NOK 177,000 profit

GLOBALTEK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GLOBALTEK EIENDOM AS

Who owns GLOBALTEK EIENDOM AS?

RIAN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GLOBALTEK EIENDOM AS?

GLOBALTEK EIENDOM AS had revenue of NOK 845,000 in 2024.

Who is the general manager of GLOBALTEK EIENDOM AS?

Roger Rian is registered as general manager of GLOBALTEK EIENDOM AS.

Where is GLOBALTEK EIENDOM AS based?

GLOBALTEK EIENDOM AS has its business address in Melhus.

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.