Jump to content

ddd

Group: 72
  • Posts

    0
  • Joined

  • Last visited

Posts posted by ddd

  1. @ReCorpH  Thanks for letting me know. Yes, I would like to know how Unibet would like to compensate for the 36 extra days they kept my money in their hands, or for the 7 days that passed since @Uni-best was so kind to post the video here, or for all the stress, harassment and false claims that the bets were lost despite overhwelming evidence I had already produced beforehand. Thank you.

  2. @Uni-bestYou, my friend, are amazing. I would've never found it. So now it's clear it was 60'.

    @ReCorpHHi there, now that we have the video, can I please get all my bets involving this particular bet get resettled asap? Coupons below:

    2521251477 / 2521249128 / 2521231590 / 2521230474 / 2521219833

    I will ask a (probably rhetorical) question... how will these 4 weeks and at least 1 day will be repayed, in terms of stress and money kept by Unibet in their bank?

    Also, good luck using that hoax of a site to trick your customers any further second from now on.

    Thank you.

  3. Hi @ReCorpH,

    As clearly depicted in my messages above, the rule invoked does not stand against all the evidence I had provided.

    When settling results [the Operator] will do its utmost to attain itself to
    information obtained first hand (during or exactly after the event has been
    concluded), through TV transmissions, streaming (web-based and through other
    sources) as well as official sites. Should this information be omitted from first
    hand viewing and/or official sources and/or there is an obvious Error in the
    information included in the sources above, the settlement of the bet offer will be
    based on other public sources.

    Of course I don't have any video (who the hell is broadcasting Saudi Arabia second league anyway?!), but I had gathered extensive evidence, including Unibet live platform, major livescore sites and Al-Jeel's official Twitter account (and we all know all of these KNOW how to round off the minutes in a soccer match - 60' is 59:00-59:59, nothing earlier, nothing later). Moreover, the site Unibet conveniently keeps invoking is making up their data, as shown in my previous bet debacle with Unibet around the Peru match. I have witnessed that first hand in other matches too, watching on live TV and seeing completely different data on their site than what I was seeing on TV in terms of various events minutes recorded. I assume they do it for traffic, since no other site is showing the seconds, but on the other hand sites like xscores.com and flashscore.com never miss to record the correct minute (rounded off properly).

    I'm even thinking of contacting Al-Jeel and asking them for a formal communication over this, but I highly doubt they'd put much effort into it just to get an unknown Romanian bettor's money in their Unibet account.

    As it stands, this is a robbery. Please tell me where I could file a formal complaint, I need this investigated by an authority whose decisions both me and Unibet would happily comply to.

    Any help from fellow Unibettors would be greatly appreciated. What can one do when a bookmaker refuses to pay their rightful winnings over their bets?

    Thank you.

  4. Also, this is the second time in less than a month that I'm facing this issue at Unibet. Please check incident 200215-004300 involving a Peruvian match. You were even broadcasting it live, I was watching and could not believe my eyes seeing the goal scored in my interval on live TV, then Unibet settling it as lost. It's clear you're doing the same here, revolving around an obscure site like livescores.biz and their convenient claim for the goal having been scored in 60:10. Let me show you this idiotic site data around my previous February incident - capture below. My bet was a goal being scored between 70:00-79:59. Guess what, a goal WAS scored in 79:57 or so. I watched that live. On Unibet. What is the scoring minute on livescores.biz? See below, 80:19!!! And i got that bet resettled and rightfully so, the goal was scored before 79:59! And now you patronize me around sites not rou ding up the scoring minute correctly, citing livescores.biz?! Oh my God, just give me a break and give me my rightful winnings. Is anyone around here using livescores.biz for anything?!

    39EE9C8E-F3E1-4297-94BC-616064E291E2.thumb.png.e1f9232ac8a2a2869f072e1ba9ffaf94.png

     

    Is Unibet doing so bad that they can't honor roughly €100 winnings? I really don't get what's going on here.

  5. Hi @RayL, we both know that is not true. First of all, xscores.com and flashscore.com are quite careful not to misrepresent the minute a goal is being scored (I tend to think it's because of possible betting issues too) and I've seen them many times altering their initial record to reflect the truth. They know very well how to round up the minutes and there is no tendency to show 60' if the scoring minute is 60:01. With flashscore.com it even happened here, they initially showed 61', then changed it to 60'. I am positive this gosl was scored before 60:00, major livescore sites show that and you can't take livescore.biz only to be true, with their claim the goal was scored in 60:10. That's, how to say it, suspiciously and conveniently precise. Also, I was following the game in Unibet's live console. Even there, the goal clearly appears to be scored in 60' and that's what I witnessed live.

    Thank you.

  6. Hi guys,

    Tagging @RayL since he was able to help me in the past, but really looking for all the support I can get.

    On Tuesday, March 10th I placed a few bets involving a goal being scored in the Saudi football match Hottain - Al-Jeel in the 30:00-59:59 interval. I was following the match in the Unibet live console and while approaching the end of that interval all odds get blocked, the graphic shows Al-Jeel scoring, the match event data records Al-Jeel's goal in 60' (which is 59:00-59:59)... and a couple minutes later all my running bets get marked as lost.

    I frantically searched the web for data around this match and found a few well known platforms confirming the goal being scored in 60' (xscores.com, flashscore.com etc.) together with Al-Jeel's Twitter account listing 60' as the scoring minute next to the goalscorer's name.

    I sent all the evidence above to Unibet support only to get a reply that they're confident the goal was scored in 61', citing obscure sites like livescores.biz and 777score.pk. Despite all the evidence I had sent it seems they aren't willing to resettle those bets as won.

    I've attached here all those screenshots, Unibet live data coverage included, hoping that you could help me further.

    To me this is most outrageous, having to investigate on my own in order to get my rightful winnings only to get my request rejected based on some obscure site data and against Unibet's own records. Not to mention the days that passed by replying back and forth without getting a satisfactory resolution.

    If you cannot help me either, please let me know where and how I could file a formal complaint. To me, what happened here can be described as robbery. And the stress Unibet have caused me is incalculable.

    For reference, the coupon ID's are the following:

     

    ID cupon 2521251477
    ID cupon 2521249128
    ID cupon 2521231590
    ID cupon 2521230474
    ID cupon 2521219833
     
    Thank you!85B2E4B5-049F-403F-B1D6-4BEBDB22D791.png.7ec254005fe4e2f7fc0cf7371d890e9d.png

     

    CFA41269-CBEB-408A-8961-1DA5A928A58C.thumb.png.870b81d164179a9547317b17f3054c9d.png

     

    02106975-EBE1-4375-9C79-51E9F5AE4E0D.thumb.png.a266637b8344b2a880693b7b6af05eec.png

     

    E8D4F3F9-4909-466B-A1AE-B6C821BB6049.thumb.png.bf55ed08415df2103966063e5b316efa.png

     

    E8769FAC-CD16-49AB-8AAD-925B130AF9D0.thumb.png.539d46be536ae65c5e4862b72b2ef3a0.png

     

    DFC51F89-537C-4214-8480-E6B924DBE520.thumb.png.2883a7821a62763852b24e36301c716f.png

     

    4592C139-B2EF-4410-8D3E-3631D83D9002.thumb.png.d07e3adcb5119bc54b798327ffb965cc.png

     

    11D68931-354B-4DCA-A475-B63BC06CF489.thumb.png.64e97ab840ddd0a7c079f0f9a5281ee1.png

     

×
×
  • Create New...