At least it looks promising. (I did not yet find a detailed technical spec for the SB16C1052PCI chip).
The final test would be this:
1) install the card
2) use PCI.EXE to check the PCI config space settings for this card.
3) If any one of the BARs (Base address registers) lists an I/O address range (instead of a memory address range), then there is a good chance that the card will be supported by COM.SYS, provided it offers the standard UART register set (which is normally true if a BAR announces I/O address range addressability).
After some more research, seems like the used chip (SB16C1052PCI) is compatible to:
https://www.nxp.com/docs/en/data-sheet/SC16C654B_654DB.pdf?The chip offers the standard UART register set (which is good) but it leaves it open to the board implementer if it is addressed via I/O address space or memory address space (it just uses 3 address bits A0,A1,A2 to select between the various registers of the UART register set but it imposes no restriction to address it via I/O address space or memory address space. The "glue logic" on the board will then map it into either I/O address space or memory address space).
If the card is a multi-UART card (which it is), the next challenge normally is to find the "step size" of the register set from one UART to the next. Normally, these are evenly spaced apart. The aforementioned spec lists 4 signals !CSA,!CSB!,!CSC,!CSD which address an individual UART (of that 4-UART chip, for 8 UARTS, it will of course be 8 signals). Typically, these signal lines either directly wire to an address bit or follow a simple logic to wire to one or more address bits (for 8 ports, that would be 3 address bits as a minimum).
My advice: buy that thing, try it out and return if it does not work. By the way, if you are also using Windows, you can also look into Windows Device manager to find out which I/O or memory addresses this card occupies.