BIZTRAC BETA
Beauty care and other beauty treatment activities

SYMRE HUDKREM AS

Org. no. 932290294 Limited company (AS) Voss Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 21,000
Equity NOK 210,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

SYMRE HUDKREM AS is registered as a limited company in Voss, Vestland with organisation number 932290294. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen skjønnhetspleie - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 21,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 21,000
Equity
NOK 210,000
Est. value
NOK 206,000

Financial health · 2025

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

Who owns SYMRE HUDKREM AS?

SILJE EEN DE AMORIZA
SYMRE HUDKREM AS
NOK 4.5m rev. · NOK 21,000 profit

SYMRE HUDKREM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYMRE HUDKREM AS

Who owns SYMRE HUDKREM AS?

SILJE EEN DE AMORIZA is the largest registered owner, with 50.0%.

What is the revenue of SYMRE HUDKREM AS?

SYMRE HUDKREM AS had revenue of NOK 4.5m in 2024.

Who is the general manager of SYMRE HUDKREM AS?

Tonje Een Danielsen is registered as general manager of SYMRE HUDKREM AS.

Where is SYMRE HUDKREM AS based?

SYMRE HUDKREM AS has its business address in Skulestadmo.

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.