BIZTRAC BETA
Activities of employment placement agencies

SILVERCON BEMANNING AS

Org. no. 928229335 Limited company (AS) Gjøvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 38,000
Equity NOK 72,000
Incorporated 2021
Share capital NOK 30,000

SILVERCON BEMANNING AS is registered as a limited company in Gjøvik, Innlandet with organisation number 928229335. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tilby bemanning-, rekruttering- og vikartjenester innenfor industri og produksjon, samt andre bransjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 38,000
Equity
NOK 72,000
Est. value
NOK 196,000

Financial health · 2025

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

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

Who owns SILVERCON BEMANNING AS?

CHRISTIAN SKOU
SILVERCON BEMANNING AS
NOK 3.4m rev. · NOK 38,000 profit

SILVERCON BEMANNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SILVERCON BEMANNING AS

Who owns SILVERCON BEMANNING AS?

CHRISTIAN SKOU is the largest registered owner, with 100.0%.

What is the revenue of SILVERCON BEMANNING AS?

SILVERCON BEMANNING AS had revenue of NOK 3.4m in 2025.

Who is the general manager of SILVERCON BEMANNING AS?

Christian Skou is registered as general manager of SILVERCON BEMANNING AS.

Where is SILVERCON BEMANNING AS based?

SILVERCON BEMANNING AS has its business address in Gjø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.