BIZTRAC BETA
Retail sale of clothing

BOUTIQUE HAMAR AS

Org. no. 926419838 Limited company (AS) Holmestrand Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 8.6m
Operating profit NOK 41,000
Equity NOK 435,000
Incorporated 2021
Employees 11
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BOUTIQUE HAMAR AS is registered as a limited company in Holmestrand, Vestfold with organisation number 926419838. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2021 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Varehandel med dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.6m in revenue and NOK 41,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.6m
Operating profit
NOK 41,000
Equity
NOK 435,000
Est. value
NOK 397,000

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.4%
Satisfactory
Equity as a share of total capital

Who owns BOUTIQUE HAMAR AS?

SMITHS HOLDING AS
BOUTIQUE HAMAR AS
NOK 8.6m rev. · NOK 41,000 profit

BOUTIQUE HAMAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOUTIQUE HAMAR AS

Who owns BOUTIQUE HAMAR AS?

SMITHS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BOUTIQUE HAMAR AS?

BOUTIQUE HAMAR AS had revenue of NOK 8.6m in 2024.

Who is the general manager of BOUTIQUE HAMAR AS?

Kenneth Smith is registered as general manager of BOUTIQUE HAMAR AS.

Where is BOUTIQUE HAMAR AS based?

BOUTIQUE HAMAR AS has its business address in Holmestrand.

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.