BIZTRAC BETA
Buying and selling of own real estate

SJT HOLDING AS

Org. no. 919567252 Limited company (AS) Indre Østfold Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 6.4m
Incorporated 2017
Share capital NOK 72,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

SJT HOLDING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 919567252. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 72,000, divided into 200 shares. The company's stated purpose is: “Investeringsselskap, herunder investering i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 6.4m
Est. value
NOK 5.9m

Financial health · 2024

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

Who owns SJT HOLDING AS?

SIMEN JØRUND TEIG
SJT HOLDING AS
NOK 0 rev. · NOK −13,000 profit

SJT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SJT HOLDING AS

Who owns SJT HOLDING AS?

SIMEN JØRUND TEIG is the largest registered owner, with 100.0%.

What is the revenue of SJT HOLDING AS?

SJT HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of SJT HOLDING AS?

Simen Jørund Teig is registered as general manager of SJT HOLDING AS.

Where is SJT HOLDING AS based?

SJT HOLDING AS has its business address in Båstad.

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.