biztrac. BETA
COMPANY REGISTER PROFILE
927829630 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

INDRESALONG AS

Org. no. 927829630 Limited company (AS) Indre Østfold Incorporated 2021 Active
Revenue 2025 NOK 2.0m
Operating profit NOK 131,000
Equity NOK 514,000
Incorporated 2021
Employees 6
Share capital NOK 30,000

INDRESALONG AS is registered as a limited company in Indre Østfold, Østfold with organisation number 927829630. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby kunder tjenester innenfor skjønnhet og hårpleie samt salg av hårprodukter. Drive agentur og handel, produksjon av forskjellige varer og tjenester, transport og lagervirksomhet med mere. Selskapet kan også investere i andre selskaper, samt i fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 131,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
▼ −7 %
Operating profit
NOK 131,000
▼ −53 %
Equity
NOK 514,000
▲ +21 %
Est. value
NOK 891,000

Financial health · 2025

Liquidity
2.21
Very good
Current assets ÷ current liabilities
Profitability
14.7%
Good
Return on total assets
Solidity
61.0%
Very good
Equity as a share of total capital

Who owns INDRESALONG AS?

INDRESALONG AS
NOK 2.0m rev. · NOK 131,000 profit

INDRESALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INDRESALONG AS

Who owns INDRESALONG AS?

Idris Amin Habash is the largest registered owner, with 100.0%.

What is the revenue of INDRESALONG AS?

INDRESALONG AS had revenue of NOK 2.0m in 2025.

Where is INDRESALONG AS based?

INDRESALONG AS has its business address in Trøgstad.

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

Report a problem

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