BIZTRAC BETA
Retail sale of other new goods

SMYKBAR OSLO AS

Org. no. 932436965 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 10.2m
Operating profit NOK 1.3m
Equity NOK 1.9m
Incorporated 2023
Employees 21
Share capital NOK 30,000

SMYKBAR OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 932436965. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2023 and has 21 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Åpne og drive butikker i Norge, hvor gjestene lager deres egne smykker under SMYKBAR sin merkevare og konsept, samt annen virksomhet innenfor kultur og fornøyelser, opplevelsesaktiviteter og produksjon av smykker eller lignende som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.2m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 10.2m
Operating profit
NOK 1.3m
Equity
NOK 1.9m
Est. value
NOK 5.2m

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
47.9%
Very good
Equity as a share of total capital

Who owns SMYKBAR OSLO AS?

SMYKBAR APS
SMYKBAR OSLO AS
NOK 10.2m rev. · NOK 1.3m profit

SMYKBAR OSLO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMYKBAR OSLO AS

Who owns SMYKBAR OSLO AS?

SMYKBAR APS is the largest registered owner, with 90.0%.

What is the revenue of SMYKBAR OSLO AS?

SMYKBAR OSLO AS had revenue of NOK 10.2m in 2025.

Who is the general manager of SMYKBAR OSLO AS?

Andrea Bjørnestad Carlsen is registered as general manager of SMYKBAR OSLO AS.

Where is SMYKBAR OSLO AS based?

SMYKBAR OSLO 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.