BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

SITJE HOLDING AS

Org. no. 921705638 Limited company (AS) Seljord Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 130,000
Equity NOK 1.6m
Incorporated 2018
Share capital NOK 30,000

SITJE HOLDING AS is registered as a limited company in Seljord, Telemark with organisation number 921705638. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, kjøp, salg og utleige av maskiner og tjenester, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 130,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 130,000
Equity
NOK 1.6m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns SITJE HOLDING AS?

TORE MÆLAND
SITJE HOLDING AS
NOK 1.2m rev. · NOK 130,000 profit

SITJE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SITJE HOLDING AS own?

SITJE HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SITJE HOLDING AS

Who owns SITJE HOLDING AS?

TORE MÆLAND is the largest registered owner, with 100.0%.

What is the revenue of SITJE HOLDING AS?

SITJE HOLDING AS had revenue of NOK 1.2m in 2025.

Where is SITJE HOLDING AS based?

SITJE HOLDING AS has its business address in Flatdal.

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.