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

GIBI EIENDOM AS

Org. no. 997818296 Limited company (AS) Gjesdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 1.0m
Equity NOK 7.7m
Incorporated 2011
Share capital NOK 6.2m

GIBI EIENDOM AS is registered as a limited company in Gjesdal, Rogaland with organisation number 997818296. 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 6.2m, divided into 6180 shares. The company's stated purpose is: “Utleie av inne og- uteareal.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▲ +7 %
Operating profit
NOK 1.0m
▲ +6 %
Equity
NOK 7.7m
▲ +3 %
Est. value
NOK 6.7m

Financial health · 2025

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.6%
Weak
Return on total assets
Solidity
33.2%
Good
Equity as a share of total capital

Who owns GIBI EIENDOM AS?

GIBI EIENDOM AS
NOK 1.5m rev. · NOK 1.0m profit

GIBI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GIBI EIENDOM AS own?

GIBI EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GIBI EIENDOM AS

Who owns GIBI EIENDOM AS?

Geir Helge Gjersdal is the largest registered owner, with 100.0%.

What is the revenue of GIBI EIENDOM AS?

GIBI EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of GIBI EIENDOM AS?

Geir Helge Gjersdal is registered as general manager of GIBI EIENDOM AS.

Where is GIBI EIENDOM AS based?

GIBI EIENDOM AS has its business address in Ålgård.

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.