BIZTRAC BETA
Other specialised construction activities n.e.c.

NSE FAGSTILLAS HOLDING AS

Org. no. 929282906 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −39,000
Equity NOK 12.8m
Incorporated 2022
Share capital NOK 71,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−39k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-07-22 Adresseendring registrert 2026-07-22.

NSE FAGSTILLAS HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 929282906. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2022. Registered share capital is NOK 71,000, divided into 35294 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å investere i aksjer, verdipapirer, fast eiendom og hva hermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −39,000
Equity
NOK 12.8m
Est. value
NOK 5.5m

Financial health · 2024

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

Who owns NSE FAGSTILLAS HOLDING AS?

NSE GRUPPEN AS
NSE FAGSTILLAS HOLDING AS
· NOK −39,000 profit

NSE FAGSTILLAS HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NSE FAGSTILLAS HOLDING AS own?

NSE FAGSTILLAS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NSE FAGSTILLAS HOLDING AS

Who owns NSE FAGSTILLAS HOLDING AS?

NSE GRUPPEN AS is the largest registered owner, with 85.0%.

Where is NSE FAGSTILLAS HOLDING AS based?

NSE FAGSTILLAS HOLDING AS has its business address in Stavanger.

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.