BIZTRAC BETA
Other personal service activities n.e.c.

SMARTHANDLINGS AS

Org. no. 915004369 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 95,000
Operating profit NOK 80,000
Equity NOK 98,000
Incorporated 2015
Share capital NOK 30,000

SMARTHANDLINGS AS is registered as a limited company in Bærum, Akershus with organisation number 915004369. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selskapsarrangør, konsulenttjenester, kursvirksomhet, rådgivning, kvalitetskontroll, internkontroll og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 95,000 in revenue and NOK 80,000 in operating profit.

Key figures · 2024

Revenue
NOK 95,000
Operating profit
NOK 80,000
Equity
NOK 98,000
Est. value
NOK 303,000

Financial health · 2024

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

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

Who owns SMARTHANDLINGS AS?

THOMAS FABIO EDVARDSEN
SMARTHANDLINGS AS
NOK 95,000 rev. · NOK 80,000 profit

SMARTHANDLINGS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMARTHANDLINGS AS

Who owns SMARTHANDLINGS AS?

THOMAS FABIO EDVARDSEN is the largest registered owner, with 100.0%.

What is the revenue of SMARTHANDLINGS AS?

SMARTHANDLINGS AS had revenue of NOK 95,000 in 2024.

Who is the general manager of SMARTHANDLINGS AS?

Thomas Fabio Edvardsen is registered as general manager of SMARTHANDLINGS AS.

Where is SMARTHANDLINGS AS based?

SMARTHANDLINGS AS has its business address in Høvik.

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.