BIZTRAC BETA
Activities of employment placement agencies

SATH AS

Org. no. 928736865 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 620,000
Incorporated 2022
Share capital NOK 120,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

SATH AS is registered as a limited company in Lillestrøm, Akershus with organisation number 928736865. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2022. Registered share capital is NOK 120,000, divided into 1200 shares. The company's stated purpose is: “Eie og forvalte aksjer og andre verdigjenstander som naturlig hører til dette, herunder delta i andre selskap, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 620,000
Est. value
NOK 892,000

Financial health · 2024

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

Who owns SATH AS?

SAGAR SINGH THIND
SATH AS
NOK 0 rev. · NOK −7,000 profit

SATH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SATH AS own?

SATH AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SATH AS

Who owns SATH AS?

SAGAR SINGH THIND is the largest registered owner, with 100.0%.

What is the revenue of SATH AS?

SATH AS had revenue of NOK 0 in 2024.

Where is SATH AS based?

SATH AS has its business address in Skjetten.

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.