BIZTRAC BETA
Computer consultancy and computer facilities management activities

TIND SOFTWARE AS

Org. no. 915181406 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 662,000
Equity NOK 1.5m
Incorporated 2015
Share capital NOK 30,000

TIND SOFTWARE AS is registered as a limited company in Bærum, Akershus with organisation number 915181406. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester og produktutvikling av programavare.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 662,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 662,000
Equity
NOK 1.5m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns TIND SOFTWARE AS?

FRANK ROGNESLIEN
TIND SOFTWARE AS
NOK 4.7m rev. · NOK 662,000 profit

TIND SOFTWARE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TIND SOFTWARE AS own?

TIND SOFTWARE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TIND SOFTWARE AS

Who owns TIND SOFTWARE AS?

FRANK ROGNESLIEN is the largest registered owner, with 50.0%.

What is the revenue of TIND SOFTWARE AS?

TIND SOFTWARE AS had revenue of NOK 4.7m in 2025.

Who is the general manager of TIND SOFTWARE AS?

Frank Rogneslien is registered as general manager of TIND SOFTWARE AS.

Where is TIND SOFTWARE AS based?

TIND SOFTWARE AS has its business address in Kolsås.

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.