BIZTRAC BETA
Painting and glazing

SVEINS MALERSERVICE AS

Org. no. 924499524 Limited company (AS) Modum Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 272,000
Equity NOK 2.3m
Incorporated 2020
Share capital NOK 30,000

SVEINS MALERSERVICE AS is registered as a limited company in Modum, Buskerud with organisation number 924499524. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Alt innen maling ute og inne, sparkling, tapetsering, gulvavretting, gulvbelegg, laminatgulv, parkett og heltregulv, og det som naturlig hører sammen med dette, samt investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 272,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 272,000
Equity
NOK 2.3m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns SVEINS MALERSERVICE AS?

ST 1 HOLDING AS
SVEINS MALERSERVICE AS
NOK 1.6m rev. · NOK 272,000 profit

SVEINS MALERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVEINS MALERSERVICE AS

Who owns SVEINS MALERSERVICE AS?

ST 1 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SVEINS MALERSERVICE AS?

SVEINS MALERSERVICE AS had revenue of NOK 1.6m in 2024.

Who is the general manager of SVEINS MALERSERVICE AS?

Svein Tore Skinstad is registered as general manager of SVEINS MALERSERVICE AS.

Where is SVEINS MALERSERVICE AS based?

SVEINS MALERSERVICE AS has its business address in Åmot.

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.