BIZTRAC BETA
Hairdressing and barber activities

SALONG GREGORIUS AS

Org. no. 920324290 Limited company (AS) Skien Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 732,000
Operating profit NOK 2,000
Equity NOK −20,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

SALONG GREGORIUS AS is registered as a limited company in Skien, Telemark with organisation number 920324290. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av frisørsalong og hva dertil står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 732,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 732,000
Operating profit
NOK 2,000
Equity
NOK −20,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns SALONG GREGORIUS AS?

HEIDI HOGSTAD BRENDEMO
SALONG GREGORIUS AS
NOK 732,000 rev. · NOK 2,000 profit

SALONG GREGORIUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALONG GREGORIUS AS

Who owns SALONG GREGORIUS AS?

HEIDI HOGSTAD BRENDEMO is the largest registered owner, with 100.0%.

What is the revenue of SALONG GREGORIUS AS?

SALONG GREGORIUS AS had revenue of NOK 732,000 in 2025.

Who is the general manager of SALONG GREGORIUS AS?

Heidi Hogstad Brendemo is registered as general manager of SALONG GREGORIUS AS.

Where is SALONG GREGORIUS AS based?

SALONG GREGORIUS AS has its business address in Skien.

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.