BIZTRAC BETA
COMPANY REGISTER PROFILE
981054202 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Hairdressing and barber activities

SAKS AS

Org. no. 981054202 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 14,000
Equity NOK 159,000
Incorporated 1999
Employees 9
Share capital NOK 101,000

SAKS AS is registered as a limited company in Oslo, Oslo with organisation number 981054202. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1999 and has 9 registered employees. Registered share capital is NOK 101,000, divided into 6750 shares. The company's stated purpose is: “Salg, handel, behandling, service, frisørvirksomhet, kursvirksomhet, konsulenttjenester, samt annen virksomhet som naturlig hører inn under det samme.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 14,000 in operating profit.

Former names: FRISØRDRIFT LILLEHAMMER AS

Key figures · 2025

Revenue
NOK 3.5m
▼ −9 %
Operating profit
NOK 14,000
▼ −83 %
Equity
NOK 159,000
▲ +6 %
Est. value
NOK 169,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.1%
Good
Equity as a share of total capital

Who owns SAKS AS?

SAKS AS
NOK 3.5m rev. · NOK 14,000 profit

SAKS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAKS AS

Who owns SAKS AS?

SVERRE ARNHEID KRISTIANSEN STEIG is the largest registered owner, with 100.0%.

What is the revenue of SAKS AS?

SAKS AS had revenue of NOK 3.5m in 2025.

Who is the general manager of SAKS AS?

Sverre Arnheid Kristiansen Steig is registered as general manager of SAKS AS.

Where is SAKS AS based?

SAKS AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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