BIZTRAC BETA
COMPANY REGISTER PROFILE
936212360 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SMEBY HOLDINGS AS

Org. no. 936212360 Limited company (AS) Etne Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 5.9m
Incorporated 2025
Share capital NOK 121,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

SMEBY HOLDINGS AS is registered as a limited company in Etne, Vestland with organisation number 936212360. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 121,000, divided into 288 shares. The company's stated purpose is: “Eierskap og investering i aksjer.”.

Key figures · 2025

Operating profit
NOK −8,000
Equity
NOK 5.9m
Est. value
NOK 6.9m

Financial health · 2025

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

Who owns SMEBY HOLDINGS AS?

SMEBY HOLDINGS AS
· NOK −8,000 profit

SMEBY HOLDINGS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SMEBY HOLDINGS AS own?

SMEBY HOLDINGS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SMEBY HOLDINGS AS

Who owns SMEBY HOLDINGS AS?

GEIR GRINDHEIM is the largest registered owner, with 100.0%.

Where is SMEBY HOLDINGS AS based?

SMEBY HOLDINGS AS has its business address in Etne.

Property

Business address Skiljebakken 25, 5590 Etne
Cadastral unit 4611-33/89/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.