BIZTRAC BETA
Preparation and spinning of textile fibres

SANDNES ULDVAREFABRIK AS

Org. no. 920467458 Limited company (AS) Klepp Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −4.8m
Equity NOK 225.3m
Incorporated 2018
Share capital NOK 150,000

Signals

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

SANDNES ULDVAREFABRIK AS is registered as a limited company in Klepp, Rogaland with organisation number 920467458. The business is classified under preparation and spinning of textile fibres (NACE 13.100). The company was incorporated in 2018. Registered share capital is NOK 150,000, divided into 150000 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av aksjer og verdipapirer, herunder lånefinansierte investeringer med verdipapirer og valuta, investering i fast eiendom, samt hva hermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −4.8m
Equity
NOK 225.3m
Est. value
NOK 442.9m

Financial health · 2024

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

Who owns SANDNES ULDVAREFABRIK AS?

TUFTEGARN AS
SANDNES ULDVAREFABRIK AS
· NOK −4.8m profit

SANDNES ULDVAREFABRIK AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SANDNES ULDVAREFABRIK AS own?

SANDNES ULDVAREFABRIK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SANDNES ULDVAREFABRIK AS

Who owns SANDNES ULDVAREFABRIK AS?

TUFTEGARN AS is the largest registered owner, with 26.0%.

Where is SANDNES ULDVAREFABRIK AS based?

SANDNES ULDVAREFABRIK AS has its business address in Kvernaland.

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.