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

TRETTEN FRISØRSALONG AS

Org. no. 991431055 Limited company (AS) Øyer Incorporated 2007 Active
Revenue 2025 NOK 2.0m
Operating profit NOK 166,000
Equity NOK 198,000
Incorporated 2007
Share capital NOK 100,000

TRETTEN FRISØRSALONG AS is registered as a limited company in Øyer, Innlandet with organisation number 991431055. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Frisørsalong, deltakelse i andre selskaper samt virksomhet forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 166,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
▲ +1 %
Operating profit
NOK 166,000
▲ +5 %
Equity
NOK 198,000
▲ +35 %
Est. value
NOK 551,000

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
8.1%
Satisfactory
Return on total assets
Solidity
9.4%
Weak
Equity as a share of total capital

Who owns TRETTEN FRISØRSALONG AS?

TRETTEN FRISØRSALONG AS
NOK 2.0m rev. · NOK 166,000 profit

TRETTEN FRISØRSALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRETTEN FRISØRSALONG AS

Who owns TRETTEN FRISØRSALONG AS?

Elin Strangstad Hagen is the largest registered owner, with 100.0%.

What is the revenue of TRETTEN FRISØRSALONG AS?

TRETTEN FRISØRSALONG AS had revenue of NOK 2.0m in 2025.

Who is the general manager of TRETTEN FRISØRSALONG AS?

Marthe Rusten Elvheim is registered as general manager of TRETTEN FRISØRSALONG AS.

Where is TRETTEN FRISØRSALONG AS based?

TRETTEN FRISØRSALONG AS has its business address in Tretten.

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.