BIZTRAC BETA
Uoppgitt

SMART BEHANDLING AS

Org. no. 929432444 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

SMART BEHANDLING AS is registered as a limited company in Stavanger, Rogaland with organisation number 929432444. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns SMART BEHANDLING AS?

FELIX MIKAL HAUGEN
SMART BEHANDLING AS
NOK 0 rev. · NOK 0 profit

SMART BEHANDLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMART BEHANDLING AS

Who owns SMART BEHANDLING AS?

FELIX MIKAL HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of SMART BEHANDLING AS?

SMART BEHANDLING AS had revenue of NOK 0 in 2025.

Who is the general manager of SMART BEHANDLING AS?

Felix Mikal Haugen is registered as general manager of SMART BEHANDLING AS.

Where is SMART BEHANDLING AS based?

SMART BEHANDLING AS has its business address in Stavanger.

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.