BIZTRAC BETA
COMPANY REGISTER PROFILE
916072104 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Hairdressing and barber activities

SIRI'S SALONG AS

Org. no. 916072104 Limited company (AS) Midtre Gauldal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 360,000
Equity NOK 692,000
Incorporated 2015
Share capital NOK 30,000

SIRI'S SALONG AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 916072104. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Frisør og skjønnhetspleie og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte å gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 360,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
▼ −3 %
Operating profit
NOK 360,000
▲ +32 %
Equity
NOK 692,000
▲ +62 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
2.78
Very good
Current assets ÷ current liabilities
Profitability
29.0%
Very good
Return on total assets
Solidity
51.9%
Very good
Equity as a share of total capital

Who owns SIRI'S SALONG AS?

SIRI'S SALONG AS
NOK 2.2m rev. · NOK 360,000 profit

SIRI'S SALONG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIRI'S SALONG AS

Who owns SIRI'S SALONG AS?

SI DIGRE HOLDING AS is the largest registered owner, with 90.0%.

What is the revenue of SIRI'S SALONG AS?

SIRI'S SALONG AS had revenue of NOK 2.2m in 2025.

Where is SIRI'S SALONG AS based?

SIRI'S SALONG AS has its business address in Støren.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.