BIZTRAC BETA
Rental and operating of own or leased real estate

DIN SALONG HUD OG HÅR AS

Org. no. 892122962 Limited company (AS) Verdal Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 430,000
Operating profit NOK 237,000
Equity NOK 160,000
Incorporated 2007
Share capital NOK 100,000

DIN SALONG HUD OG HÅR AS is registered as a limited company in Verdal, Trøndelag with organisation number 892122962. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom og annen virksomhet som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 430,000 in revenue and NOK 237,000 in operating profit.

Key figures · 2024

Revenue
NOK 430,000
Operating profit
NOK 237,000
Equity
NOK 160,000
Est. value
NOK 549,000

Financial health · 2024

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

Who owns DIN SALONG HUD OG HÅR AS?

GUNNVOR MØST EGGEN
DIN SALONG HUD OG HÅR AS
NOK 430,000 rev. · NOK 237,000 profit

DIN SALONG HUD OG HÅR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIN SALONG HUD OG HÅR AS

Who owns DIN SALONG HUD OG HÅR AS?

GUNNVOR MØST EGGEN is the largest registered owner, with 100.0%.

What is the revenue of DIN SALONG HUD OG HÅR AS?

DIN SALONG HUD OG HÅR AS had revenue of NOK 430,000 in 2024.

Who is the general manager of DIN SALONG HUD OG HÅR AS?

Gunnvor Møst Eggen is registered as general manager of DIN SALONG HUD OG HÅR AS.

Where is DIN SALONG HUD OG HÅR AS based?

DIN SALONG HUD OG HÅR AS has its business address in Verdal.

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.