biztrac. BETA
COMPANY REGISTER PROFILE
917331383 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

TISLE AS

Org. no. 917331383 Limited company (AS) Drammen Incorporated 2016 Active
Revenue 2025 NOK 0
Operating profit NOK −363,000
Equity NOK 736,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

TISLE AS is registered as a limited company in Drammen, Buskerud with organisation number 917331383. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innen administrasjon, logistikk, innkjøp og kontrakt samt forvaltning av kapital herunder eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −363,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −363,000
▼ −170 %
Equity
NOK 736,000
▼ −32 %
Est. value
NOK 493,000

Financial health · 2025

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
-7.6%
Not satisfactory
Return on total assets
Solidity
34.8%
Good
Equity as a share of total capital

Who owns TISLE AS?

TISLE AS
NOK 0 rev. · NOK −363,000 profit

TISLE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TISLE AS

Who owns TISLE AS?

Torleiv Tislevoll is the largest registered owner, with 100.0%.

What is the revenue of TISLE AS?

TISLE AS had revenue of NOK 0 in 2025.

Who is the general manager of TISLE AS?

Torleiv Tislevoll is registered as general manager of TISLE AS.

Where is TISLE AS based?

TISLE AS has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.