BIZTRAC BETA
Rental and operating of own or leased real estate

GAUTE ROSTRUP EIENDOM AS

Org. no. 984399804 Limited company (AS) Sandnes Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 601,000
Equity NOK 4.0m
Incorporated 2002
Share capital NOK 100,000

GAUTE ROSTRUP EIENDOM AS is registered as a limited company in Sandnes, Rogaland with organisation number 984399804. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av eiendom og hva hermed står i forbindlese.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 601,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 601,000
Equity
NOK 4.0m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns GAUTE ROSTRUP EIENDOM AS?

GAUTE ROSTRUP KUNSTFORMIDLING OG EIENDOM AS
GAUTE ROSTRUP EIENDOM AS
NOK 1.2m rev. · NOK 601,000 profit

GAUTE ROSTRUP EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAUTE ROSTRUP EIENDOM AS

Who owns GAUTE ROSTRUP EIENDOM AS?

GAUTE ROSTRUP KUNSTFORMIDLING OG EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of GAUTE ROSTRUP EIENDOM AS?

GAUTE ROSTRUP EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of GAUTE ROSTRUP EIENDOM AS?

Stig Ruben Thuv is registered as general manager of GAUTE ROSTRUP EIENDOM AS.

Where is GAUTE ROSTRUP EIENDOM AS based?

GAUTE ROSTRUP EIENDOM AS has its business address in Sandnes.

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.