BIZTRAC BETA
Rental and operating of own or leased real estate

HAMRE CONSULTING AS

Org. no. 933649261 Limited company (AS) Færder Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK 6,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

HAMRE CONSULTING AS is registered as a limited company in Færder, Vestfold with organisation number 933649261. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utleie fast eiendom og økonomisk rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 6,000
Est. value
NOK 5,000

Financial health · 2024

Liquidity
-0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7240.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HAMRE CONSULTING AS?

STIG HAMRE
HAMRE CONSULTING AS
NOK 0 rev. · NOK −24,000 profit

HAMRE CONSULTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAMRE CONSULTING AS

Who owns HAMRE CONSULTING AS?

STIG HAMRE is the largest registered owner, with 50.0%.

What is the revenue of HAMRE CONSULTING AS?

HAMRE CONSULTING AS had revenue of NOK 0 in 2024.

Who is the general manager of HAMRE CONSULTING AS?

Stig Hamre is registered as general manager of HAMRE CONSULTING AS.

Where is HAMRE CONSULTING AS based?

HAMRE CONSULTING AS has its business address in Skallestad.

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.