BIZTRAC BETA
Retail sale of clothing

BOUTIQUE GRENSEN AS

Org. no. 917999139 Limited company (AS) Holmestrand Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 20.0m
Operating profit NOK 1.7m
Equity NOK 843,000
Incorporated 2016
Employees 9
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 GRENSEN AS is registered as a limited company in Holmestrand, Vestfold with organisation number 917999139. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2016 and has 9 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 20.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 20.0m
Operating profit
NOK 1.7m
Equity
NOK 843,000
Est. value
NOK 6.5m

Financial health · 2024

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

Who owns BOUTIQUE GRENSEN AS?

SMITHS HOLDING AS
BOUTIQUE GRENSEN AS
NOK 20.0m rev. · NOK 1.7m profit

BOUTIQUE GRENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOUTIQUE GRENSEN AS

Who owns BOUTIQUE GRENSEN AS?

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

What is the revenue of BOUTIQUE GRENSEN AS?

BOUTIQUE GRENSEN AS had revenue of NOK 20.0m in 2024.

Who is the general manager of BOUTIQUE GRENSEN AS?

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

Where is BOUTIQUE GRENSEN AS based?

BOUTIQUE GRENSEN 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.