BIZTRAC BETA
Hairdressing and barber activities

KE FRISØR AS

Org. no. 920934439 Limited company (AS) Modum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 694,000
Operating profit NOK 5,000
Equity NOK 5,000
Incorporated 2018
Share capital NOK 30,000

KE FRISØR AS is registered as a limited company in Modum, Buskerud with organisation number 920934439. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Frisørtjenester og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap 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 694,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 694,000
Operating profit
NOK 5,000
Equity
NOK 5,000
Est. value
NOK 26,000

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.4%
Weak
Equity as a share of total capital

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

Who owns KE FRISØR AS?

KRISTINE NÆRLAND EVENSEN
KE FRISØR AS
NOK 694,000 rev. · NOK 5,000 profit

KE FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KE FRISØR AS

Who owns KE FRISØR AS?

KRISTINE NÆRLAND EVENSEN is the largest registered owner, with 100.0%.

What is the revenue of KE FRISØR AS?

KE FRISØR AS had revenue of NOK 694,000 in 2025.

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

Kristine Nærland Evensen is registered as general manager of KE FRISØR AS.

Where is KE FRISØR AS based?

KE FRISØR AS has its business address in Åmot.

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.