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

GYNTOR EIENDOM AS

Org. no. 917696489 Limited company (AS) Haugesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 114,000
Operating profit NOK 37,000
Equity NOK 103,000
Incorporated 2016
Share capital NOK 75,000

GYNTOR EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 917696489. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 75,000, divided into 150 shares. The company's stated purpose is: “Kjøp, salg, utleie og drift av fast eiendom, samt virksomhet som naturlig følger med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 114,000 in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 114,000
▲ +0 %
Operating profit
NOK 37,000
▼ −41 %
Equity
NOK 103,000
▼ −8 %
Est. value
NOK 125,000

Financial health · 2025

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

Who owns GYNTOR EIENDOM AS?

GYNTOR EIENDOM AS
NOK 114,000 rev. · NOK 37,000 profit

GYNTOR EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GYNTOR EIENDOM AS

Who owns GYNTOR EIENDOM AS?

Yngve Furseth is the largest registered owner, with 33.3%.

What is the revenue of GYNTOR EIENDOM AS?

GYNTOR EIENDOM AS had revenue of NOK 114,000 in 2025.

Who is the general manager of GYNTOR EIENDOM AS?

Torleif Vestre is registered as general manager of GYNTOR EIENDOM AS.

Where is GYNTOR EIENDOM AS based?

GYNTOR EIENDOM AS has its business address in Haugesund.

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.