EU

Investor profile

Emil Urmanshin

Operator angel

London·United Kingdom1known investment

An operator angel based in London, England, United Kingdom, Emil Urmanshin has one known investment, Due.

Is Emil Urmanshin a fit for your startup?

Paste your website. AI checks the fit and scores every other investor too.

Investment focus

Stage
Seed
Sector
FinTech

Contacts

emi***@***.comPhone number on fileLinkedIn profile on fileAvailable after registration.
Get contact

Emil Urmanshin portfolio company (1)

  • Due

Investor Profile

The listing covers sector FinTech, and focus area Crypto Infrastructure. Startups operating in these areas may find Emil Urmanshin relevant.

The stage tag on this profile is Seed.

The portfolio and focus above give founders context on whether Emil Urmanshin matches their raise.

Similar investors

Showing 20 of 100

Frequently asked questions

Who is Emil Urmanshin?

Emil Urmanshin is an operator angel based in London, England, United Kingdom with one known investment on file, Due. The sections above list the sectors and stages attached to that record.

What does Emil Urmanshin invest in?

Listed sectors include FinTech; listed focus areas include Crypto Infrastructure. Those tags come from the companies attached to this profile, so they read as a record of what has been backed rather than a stated preference for what comes next.

What stage does Emil Urmanshin invest at?

The database lists Emil Urmanshin for Seed rounds. Stage is the strongest single filter when you build a target list: an investor with no record at your stage rarely starts with you.

How do I contact Emil Urmanshin?

An email address, a phone number and a LinkedIn page are on file for Emil Urmanshin. 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 6 September 2026 · How this data is built · Report a correction or request removal