BIZTRAC BETA
Beauty care and other beauty treatment activities

ATHINA FRISØRENE AS

Org. no. 889467142 Limited company (AS) Trondheim Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 47,000
Equity NOK −87,000
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−87k kr).

ATHINA FRISØRENE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 889467142. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salong for hårbehandling og annen tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 47,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 47,000
Equity
NOK −87,000
Est. value
NOK 343,000

Financial health · 2025

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-46.0%
Weak
Equity as a share of total capital

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

Who owns ATHINA FRISØRENE AS?

LIV SELBÆK
ATHINA FRISØRENE AS
NOK 1.8m rev. · NOK 47,000 profit

ATHINA FRISØRENE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ATHINA FRISØRENE AS

Who owns ATHINA FRISØRENE AS?

LIV SELBÆK is the largest registered owner, with 100.0%.

What is the revenue of ATHINA FRISØRENE AS?

ATHINA FRISØRENE AS had revenue of NOK 1.8m in 2025.

Who is the general manager of ATHINA FRISØRENE AS?

Liv Selbæk is registered as general manager of ATHINA FRISØRENE AS.

Where is ATHINA FRISØRENE AS based?

ATHINA FRISØRENE 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.