BIZTRAC BETA
Beauty care and other beauty treatment activities

BISLETT HUDPLEIE AS

Org. no. 990336415 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 59,000
Equity NOK 105,000
Incorporated 2006
Share capital NOK 100,000

BISLETT HUDPLEIE AS is registered as a limited company in Oslo, Oslo with organisation number 990336415. 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: “Salg av hudpleie/-fotpleietjenester og tjenester og produkter relatert til dette, samt å drive generell investeringsvirksomhet gjennom eierskap i aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 59,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 59,000
Equity
NOK 105,000
Est. value
NOK 276,000

Financial health · 2025

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

Who owns BISLETT HUDPLEIE AS?

LINE THERESE SKARPSNO
BISLETT HUDPLEIE AS
NOK 1.4m rev. · NOK 59,000 profit

BISLETT HUDPLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BISLETT HUDPLEIE AS

Who owns BISLETT HUDPLEIE AS?

LINE THERESE SKARPSNO is the largest registered owner, with 100.0%.

What is the revenue of BISLETT HUDPLEIE AS?

BISLETT HUDPLEIE AS had revenue of NOK 1.4m in 2025.

Who is the general manager of BISLETT HUDPLEIE AS?

Line Therese Skarpsno is registered as general manager of BISLETT HUDPLEIE AS.

Where is BISLETT HUDPLEIE AS based?

BISLETT HUDPLEIE 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 15.06.2026.

Report a problem

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