BIZTRAC BETA
Rental and operating of own or leased real estate

GEFO EIENDOM AS

Org. no. 915330037 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 808,000
Operating profit NOK 569,000
Equity NOK 5.0m
Incorporated 2015
Share capital NOK 40,000

GEFO EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 915330037. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Eie og forvalte aksjer, obligasjoner, andre verdipapirer og egenkapitalinstrumenter, eie og drive fast eiendom, deltakelse i selskaper med tilsvarende virksomhet samt annen virksomhet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 808,000 in revenue and NOK 569,000 in operating profit.

Key figures · 2024

Revenue
NOK 808,000
Operating profit
NOK 569,000
Equity
NOK 5.0m
Est. value
NOK 4.5m

Financial health · 2024

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
66.5%
Very good
Equity as a share of total capital

Who owns GEFO EIENDOM AS?

GEIR JOHNNY LERUM
GEFO EIENDOM AS
NOK 808,000 rev. · NOK 569,000 profit

GEFO EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GEFO EIENDOM AS

Who owns GEFO EIENDOM AS?

GEIR JOHNNY LERUM is the largest registered owner, with 50.0%.

What is the revenue of GEFO EIENDOM AS?

GEFO EIENDOM AS had revenue of NOK 808,000 in 2024.

Who is the general manager of GEFO EIENDOM AS?

Frode Nøttveit is registered as general manager of GEFO EIENDOM AS.

Where is GEFO EIENDOM AS based?

GEFO EIENDOM AS has its business address in Bergen.

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.