BIZTRAC BETA
Buying and selling of own real estate

GEFRO FINANS AS

Org. no. 992052473 Limited company (AS) Randaberg Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −327,000
Equity NOK 76.7m
Incorporated 2007
Share capital NOK 55.7m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−327k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GEFRO FINANS AS is registered as a limited company in Randaberg, Rogaland with organisation number 992052473. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2007. Registered share capital is NOK 55.7m, divided into 6250 shares. The company's stated purpose is: “Forestå kjøp og salg av aksjer, andre verdipapirer og fast eiendom samt tilknyttet virksomhet. Selskapet kan også delta i andre selskaper med tilsvarende virksomhet.”.

Key figures · 2024

Operating profit
NOK −327,000
Equity
NOK 76.7m
Est. value
NOK 70.0m

Financial health · 2024

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
86.5%
Very good
Equity as a share of total capital

Who owns GEFRO FINANS AS?

RUNESTAD INVESTERING AS
GEFRO FINANS AS
· NOK −327,000 profit

GEFRO FINANS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GEFRO FINANS AS own?

GEFRO FINANS AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about GEFRO FINANS AS

Who owns GEFRO FINANS AS?

RUNESTAD INVESTERING AS is the largest registered owner, with 50.0%.

Who is the general manager of GEFRO FINANS AS?

Rune Runestad is registered as general manager of GEFRO FINANS AS.

Where is GEFRO FINANS AS based?

GEFRO FINANS AS has its business address in Randaberg.

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.