BIZTRAC BETA
COMPANY REGISTER PROFILE
998578639 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

HAMRE UTLEIE AS

Org. no. 998578639 Limited company (AS) Vindafjord Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 516,000
Operating profit NOK 159,000
Equity NOK 383,000
Incorporated 2012
Share capital NOK 50,000

HAMRE UTLEIE AS is registered as a limited company in Vindafjord, Rogaland with organisation number 998578639. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Utleie av boliger, hytter og utstyr og naturlig tilhørende virksomhet,herunder investering i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 516,000 in revenue and NOK 159,000 in operating profit.

Key figures · 2025

Revenue
NOK 516,000
▼ −21 %
Operating profit
NOK 159,000
▼ −26 %
Equity
NOK 383,000
▲ +47 %
Est. value
NOK 668,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
7.3%
Satisfactory
Return on total assets
Solidity
15.3%
Satisfactory
Equity as a share of total capital

Who owns HAMRE UTLEIE AS?

HAMRE UTLEIE AS
NOK 516,000 rev. · NOK 159,000 profit

HAMRE UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAMRE UTLEIE AS

Who owns HAMRE UTLEIE AS?

ØYVIND HAMRE is the largest registered owner, with 100.0%.

What is the revenue of HAMRE UTLEIE AS?

HAMRE UTLEIE AS had revenue of NOK 516,000 in 2025.

Who is the general manager of HAMRE UTLEIE AS?

Øyvind Hamre is registered as general manager of HAMRE UTLEIE AS.

Where is HAMRE UTLEIE AS based?

HAMRE UTLEIE AS has its business address in Vikedal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.