BIZTRAC BETA
Hairdressing and barber activities

STEBI AS

Org. no. 918771824 Limited company (AS) Midt-Telemark Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −32,000
Equity NOK −85,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−85k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−32k kr).

STEBI AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 918771824. 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 300 shares. The company's stated purpose is: “Frisørvirksomhet og skjønnhetspleie, salg av varer innenfor frisør og skjønnhetsbransjen samt annet som naturlig hører innunder dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −32,000
Equity
NOK −85,000

Financial health · 2025

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

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

Who owns STEBI AS?

BIRGITTE KLEPPE VERPE
STEBI AS
NOK 1.3m rev. · NOK −32,000 profit

STEBI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STEBI AS

Who owns STEBI AS?

BIRGITTE KLEPPE VERPE is the largest registered owner, with 70.0%.

What is the revenue of STEBI AS?

STEBI AS had revenue of NOK 1.3m in 2025.

Who is the general manager of STEBI AS?

Birgitte Kleppe Verpe is registered as general manager of STEBI AS.

Where is STEBI AS based?

STEBI AS has its business address in Bø I Telemark.

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.