BIZTRAC BETA
Business and other management consultancy activities

WERGELAND PROSESSPARTNER AS

Org. no. 919439106 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 27,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

WERGELAND PROSESSPARTNER AS is registered as a limited company in Oslo, Oslo with organisation number 919439106. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Organisasjonsutvikling, rådgivning og undervisning og annet som naturlig faller sammen med dette.”.

Key figures · 2024

Operating profit
NOK −1,000
Equity
NOK 27,000
Est. value
NOK 43,000

Financial health · 2024

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

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

Who owns WERGELAND PROSESSPARTNER AS?

SIVWAS AS
WERGELAND PROSESSPARTNER AS
· NOK −1,000 profit

WERGELAND PROSESSPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WERGELAND PROSESSPARTNER AS

Who owns WERGELAND PROSESSPARTNER AS?

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

Who is the general manager of WERGELAND PROSESSPARTNER AS?

Siv Hege Wergeland is registered as general manager of WERGELAND PROSESSPARTNER AS.

Where is WERGELAND PROSESSPARTNER AS based?

WERGELAND PROSESSPARTNER AS has its business address in Oslo.

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.