BIZTRAC BETA
Other business support service activities n.e.c.

SETPRO KOMMUNALE TJENESTER AS

Org. no. 927304910 Limited company (AS) Evje Og Hornnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 200,000
Operating profit NOK −33,000
Equity NOK 201,000
Incorporated 2021
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−33k kr).

SETPRO KOMMUNALE TJENESTER AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 927304910. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2021. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Selge tjenester og produkter til kommunale virksomheter gjennom ordningen utvidet kommunal egenregi.”. The most recent filed accounts, for the 2024 financial year, show NOK 200,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2024

Revenue
NOK 200,000
Operating profit
NOK −33,000
Equity
NOK 201,000
Est. value
NOK 228,000

Financial health · 2024

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

Who owns SETPRO KOMMUNALE TJENESTER AS?

SETPRO AS
SETPRO KOMMUNALE TJENESTER AS
NOK 200,000 rev. · NOK −33,000 profit

SETPRO KOMMUNALE TJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SETPRO KOMMUNALE TJENESTER AS

Who owns SETPRO KOMMUNALE TJENESTER AS?

SETPRO AS is the largest registered owner, with 100.0%.

What is the revenue of SETPRO KOMMUNALE TJENESTER AS?

SETPRO KOMMUNALE TJENESTER AS had revenue of NOK 200,000 in 2024.

Where is SETPRO KOMMUNALE TJENESTER AS based?

SETPRO KOMMUNALE TJENESTER AS has its business address in Evje.

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.