biztrac. BETA
COMPANY REGISTER PROFILE
929168062 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

SAWJIG AS

Org. no. 929168062 Limited company (AS) Færder Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK −1,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

SAWJIG AS is registered as a limited company in Færder, Vestfold with organisation number 929168062. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og produksjon av verktøy og hjelpemidler til bygge industrien. Formålet omfatter også kjøp og salg av eiendom, herunder import og eksport, konsulentvirksomhet og investerings- og plasseringsvirksomhet, herunder investering i, samt deltakelse i, selskapet med liknende forhold som nevnt foran.”.

Key figures · 2025

Operating profit
NOK −5,000
▲ +37 %
Equity
NOK −1,000
▼ −139 %

Financial health · 2025

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

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

Who owns SAWJIG AS?

SAWJIG AS
· NOK −5,000 profit

SAWJIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAWJIG AS

Who owns SAWJIG AS?

Henrik Vidnes Doksrød is the largest registered owner, with 100.0%.

Who is the general manager of SAWJIG AS?

Henrik Vidnes Doksrød is registered as general manager of SAWJIG AS.

Where is SAWJIG AS based?

SAWJIG AS has its business address in Nøtterøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.