BIZTRAC BETA
Rental and operating of own or leased real estate

TISET INVEST AS

Org. no. 917198640 Limited company (AS) Rindal Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 11,000
Operating profit NOK −6,000
Equity NOK 338,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

TISET INVEST AS is registered as a limited company in Rindal, Trøndelag with organisation number 917198640. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er rørleggervirksomhet, bilverksted og andre håndverkstjenester. Kjøp, salg, utvikling og utleie av eiendom samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 11,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 11,000
Operating profit
NOK −6,000
Equity
NOK 338,000
Est. value
NOK 247,000

Financial health · 2024

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

Who owns TISET INVEST AS?

RUNE TISET
TISET INVEST AS
NOK 11,000 rev. · NOK −6,000 profit

TISET INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TISET INVEST AS

Who owns TISET INVEST AS?

RUNE TISET is the largest registered owner, with 100.0%.

What is the revenue of TISET INVEST AS?

TISET INVEST AS had revenue of NOK 11,000 in 2024.

Who is the general manager of TISET INVEST AS?

Rune Tiset is registered as general manager of TISET INVEST AS.

Where is TISET INVEST AS based?

TISET INVEST AS has its business address in Rindal.

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.