BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

SMEDHEIM AS

Org. no. 930724645 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 55.1m
Operating profit NOK 24,000
Equity NOK 935,000
Incorporated 2023
Employees 23
Share capital NOK 500,000

SMEDHEIM AS is registered as a limited company in Bærum, Akershus with organisation number 930724645. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023 and has 23 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 55.1m in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 55.1m
Operating profit
NOK 24,000
Equity
NOK 935,000
Est. value
NOK 555,000

Financial health · 2025

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

Who owns SMEDHEIM AS?

HERMAN SMEDHEIM BJERKLUND
SMEDHEIM AS
NOK 55.1m rev. · NOK 24,000 profit

SMEDHEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMEDHEIM AS

Who owns SMEDHEIM AS?

HERMAN SMEDHEIM BJERKLUND is the largest registered owner, with 100.0%.

What is the revenue of SMEDHEIM AS?

SMEDHEIM AS had revenue of NOK 55.1m in 2025.

Who is the general manager of SMEDHEIM AS?

Stine Eriksen is registered as general manager of SMEDHEIM AS.

Where is SMEDHEIM AS based?

SMEDHEIM AS has its business address in Sandvika.

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.