BIZTRAC BETA
Combined facilities support activities

TI TJENESTER AS

Org. no. 832485292 Limited company (AS) Grimstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 70,000
Operating profit NOK 4,000
Equity NOK 54,000
Incorporated 2023
Share capital NOK 30,000

TI TJENESTER AS is registered as a limited company in Grimstad, Agder with organisation number 832485292. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen vaktmesterarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 70,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2024

Revenue
NOK 70,000
Operating profit
NOK 4,000
Equity
NOK 54,000
Est. value
NOK 47,000

Financial health · 2025

Liquidity
-4.82
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
97.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TI TJENESTER AS?

KIM KROSSHØL IGLAND
TI TJENESTER AS
NOK 70,000 rev. · NOK 4,000 profit

TI TJENESTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TI TJENESTER AS

Who owns TI TJENESTER AS?

KIM KROSSHØL IGLAND is the largest registered owner, with 50.0%.

What is the revenue of TI TJENESTER AS?

TI TJENESTER AS had revenue of NOK 70,000 in 2024.

Who is the general manager of TI TJENESTER AS?

Simen Tveit is registered as general manager of TI TJENESTER AS.

Where is TI TJENESTER AS based?

TI TJENESTER AS has its business address in Grimstad.

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.