BIZTRAC BETA
Hairdressing and barber activities

AM SALONGEN AS

Org. no. 816723892 Limited company (AS) Larvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 29,000
Equity NOK −31,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−31k kr).

AM SALONGEN AS is registered as a limited company in Larvik, Vestfold with organisation number 816723892. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisering og annen skjønnhetspleie, samt virksomhet som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 29,000
Equity
NOK −31,000
Est. value
NOK 221,000

Financial health · 2025

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

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

Who owns AM SALONGEN AS?

MEHVAN MOHAMMAD SALIM AMEDI
AM SALONGEN AS
NOK 2.0m rev. · NOK 29,000 profit

AM SALONGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AM SALONGEN AS

Who owns AM SALONGEN AS?

MEHVAN MOHAMMAD SALIM AMEDI is the largest registered owner, with 100.0%.

What is the revenue of AM SALONGEN AS?

AM SALONGEN AS had revenue of NOK 2.0m in 2025.

Who is the general manager of AM SALONGEN AS?

Mehvan Mohammad Salim Amedi is registered as general manager of AM SALONGEN AS.

Where is AM SALONGEN AS based?

AM SALONGEN AS has its business address in Larvik.

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.