Investor profile
Tihomir Dyankov
Private equity & Chief Investment Officer & Partner at INVENIO Partners
Tihomir Dyankov is a Chief Investment Officer & Partner at INVENIO Partners, whose known portfolio counts 2 companies.
Is Tihomir Dyankov a fit for your startup?
Paste your website. AI checks the fit and scores every other investor too.
Investment focus
Contacts
Affiliated funds' portfolios
Chief Investment Officer & Partner at INVENIO Partners, whose known portfolio counts 2 companies
- Nasekomo
- Software Group
Investor Profile
INVENIO Partners appears in Growth, Seed and Series A rounds across its known deals.
What the affiliated firm has backed is the closest available signal on whether Tihomir Dyankov is worth approaching.
Colleagues at INVENIO Partners
Frequently asked questions
Who is Tihomir Dyankov?
Tihomir Dyankov is a private equity investor based in Lozenets, Bulgaria, listed as Chief Investment Officer & Partner at INVENIO Partners. The known portfolio of that firm counts 2 companies. That portfolio belongs to the firm, not to Tihomir Dyankov personally.
What stage does Tihomir Dyankov invest at?
INVENIO Partners appears in Growth, Seed and Series A rounds across its known deals, and Tihomir Dyankov is listed there as Chief Investment Officer & Partner. Stage is the strongest single filter when you build a target list: an investor with no record at your stage rarely starts with you.
Which firm is Tihomir Dyankov listed at?
Tihomir Dyankov is listed as Chief Investment Officer & Partner at INVENIO Partners. 3 other people in the database share a firm with Tihomir Dyankov.
How do I contact Tihomir Dyankov?
An email address, a phone number and a LinkedIn page are on file for Tihomir Dyankov. The address stays masked on this page and is readable inside RaiseHunt after you create an account.
Skip the browsing. Let AI find your ideal investors in one minute.
Paste your startup website and AI picks your best-fit investors out of 135,000+ profiles.
Data: RaiseHunt investor dataset · Snapshot 5 September 2026 · How this data is built · Report a correction or request removal