BIZTRAC BETA
Other captive investment companies

SMÅBERG AS

Org. no. 919512393 Limited company (AS) Stavanger Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 429,000
Operating profit NOK 102,000
Equity NOK 9.2m
Incorporated 2017
Share capital NOK 323,000

SMÅBERG AS is registered as a limited company in Stavanger, Rogaland with organisation number 919512393. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 323,000, divided into 16 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investering i aksjer og andeler og deltakelse i andre selskap, og annet som står i naturlig forbindelse med dette. I tillegg drive med konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 429,000 in revenue and NOK 102,000 in operating profit.

Key figures · 2025

Revenue
NOK 429,000
Operating profit
NOK 102,000
Equity
NOK 9.2m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns SMÅBERG AS?

ERLING VAULA
SMÅBERG AS
NOK 429,000 rev. · NOK 102,000 profit

SMÅBERG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SMÅBERG AS own?

SMÅBERG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SMÅBERG AS

Who owns SMÅBERG AS?

ERLING VAULA is the largest registered owner, with 100.0%.

What is the revenue of SMÅBERG AS?

SMÅBERG AS had revenue of NOK 429,000 in 2025.

Who is the general manager of SMÅBERG AS?

Erling Vaula is registered as general manager of SMÅBERG AS.

Where is SMÅBERG AS based?

SMÅBERG AS has its business address in Rennesøy.

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.