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

ELA FRISØR AS

Org. no. 914836123 Limited company (AS) Trondheim Incorporated 2015 Active
Revenue 2025 NOK 4.5m
Operating profit NOK −157,000
Equity NOK 1.1m
Incorporated 2015
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−157k kr).

ELA FRISØR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914836123. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2015 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisering, hårpleie og annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK −157,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
▲ +0 %
Operating profit
NOK −157,000
▲ +10 %
Equity
NOK 1.1m
▲ +2 %
Est. value
NOK 908,000

Financial health · 2025

Liquidity
1.77
Good
Current assets ÷ current liabilities
Profitability
-8.1%
Not satisfactory
Return on total assets
Solidity
65.4%
Very good
Equity as a share of total capital

Who owns ELA FRISØR AS?

ELA FRISØR AS
NOK 4.5m rev. · NOK −157,000 profit

ELA FRISØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ELA FRISØR AS

Who owns ELA FRISØR AS?

Marte Eriksen is the largest registered owner, with 53.3%.

What is the revenue of ELA FRISØR AS?

ELA FRISØR AS had revenue of NOK 4.5m in 2025.

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

Marte Eriksen is registered as general manager of ELA FRISØR AS.

Where is ELA FRISØR AS based?

ELA FRISØR AS has its business address in Trondheim.

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.