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

BABEL FRISØR AS

Org. no. 924925809 Limited company (AS) Fredrikstad Incorporated 2020 Active
Revenue 2025 NOK 1.4m
Operating profit NOK 19,000
Equity NOK 93,000
Incorporated 2020
Share capital NOK 30,000

BABEL FRISØR AS is registered as a limited company in Fredrikstad, Østfold with organisation number 924925809. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Frisering og annen skjønnhetspleie og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 19,000 in operating profit.

Former names: FLIGHT MODE MUSIC NORWAY AS

Key figures · 2025

Revenue
NOK 1.4m
▲ +3 %
Operating profit
NOK 19,000
▲ +68 %
Equity
NOK 93,000
▲ +20 %
Est. value
NOK 131,000

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
6.0%
Weak
Return on total assets
Solidity
30.6%
Weak
Equity as a share of total capital

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

Who owns BABEL FRISØR AS?

BABEL FRISØR AS
NOK 1.4m rev. · NOK 19,000 profit

BABEL FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BABEL FRISØR AS

Who owns BABEL FRISØR AS?

Hawry Ghareeb is the largest registered owner, with 100.0%.

What is the revenue of BABEL FRISØR AS?

BABEL FRISØR AS had revenue of NOK 1.4m in 2025.

Who is the general manager of BABEL FRISØR AS?

Hawry Ghareeb is registered as general manager of BABEL FRISØR AS.

Where is BABEL FRISØR AS based?

BABEL FRISØR AS has its business address in Fredrikstad.

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.