BIZTRAC BETA
Other technical consultancy

TIND TEKNOLOGI AS

Org. no. 920589049 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 674,000
Equity NOK 7.0m
Incorporated 2018
Share capital NOK 50,000

TIND TEKNOLOGI AS is registered as a limited company in Drammen, Buskerud with organisation number 920589049. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Konsulent og rådgivning innen teknisk kompetanse. Selskapet kan eie aksjer og delta i lignende eller beslektede virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 674,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 674,000
Equity
NOK 7.0m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns TIND TEKNOLOGI AS?

KNUT IVAR GJERDE
TIND TEKNOLOGI AS
NOK 1.7m rev. · NOK 674,000 profit

TIND TEKNOLOGI AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TIND TEKNOLOGI AS own?

TIND TEKNOLOGI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TIND TEKNOLOGI AS

Who owns TIND TEKNOLOGI AS?

KNUT IVAR GJERDE is the largest registered owner, with 62.4%.

What is the revenue of TIND TEKNOLOGI AS?

TIND TEKNOLOGI AS had revenue of NOK 1.7m in 2024.

Who is the general manager of TIND TEKNOLOGI AS?

Knut Ivar Gjerde is registered as general manager of TIND TEKNOLOGI AS.

Where is TIND TEKNOLOGI AS based?

TIND TEKNOLOGI 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 15.06.2026.

Report a problem

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