BIZTRAC BETA
Hairdressing and barber activities

PYRAMIDEN FRISØR AS

Org. no. 918906096 Limited company (AS) Luster Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 185,000
Operating profit NOK −562,000
Equity NOK 777,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

PYRAMIDEN FRISØR AS is registered as a limited company in Luster, Vestland with organisation number 918906096. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisør og annen skjønnhetspleie samt det som naturleg står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 185,000 in revenue and NOK −562,000 in operating profit.

Key figures · 2025

Revenue
NOK 185,000
Operating profit
NOK −562,000
Equity
NOK 777,000
Est. value
NOK 521,000

Financial health · 2025

Liquidity
7.92
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.4%
Very good
Equity as a share of total capital

Who owns PYRAMIDEN FRISØR AS?

JANNE GRETHE EIDE
PYRAMIDEN FRISØR AS
NOK 185,000 rev. · NOK −562,000 profit

PYRAMIDEN FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PYRAMIDEN FRISØR AS

Who owns PYRAMIDEN FRISØR AS?

JANNE GRETHE EIDE is the largest registered owner, with 100.0%.

What is the revenue of PYRAMIDEN FRISØR AS?

PYRAMIDEN FRISØR AS had revenue of NOK 185,000 in 2025.

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

Janne Grethe Eide is registered as general manager of PYRAMIDEN FRISØR AS.

Where is PYRAMIDEN FRISØR AS based?

PYRAMIDEN FRISØR AS has its business address in Gaupne.

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.