Rhacophorus bimaculatus (Peters, 1867)

Class: Amphibia > Order: Anura > Family: Rhacophoridae > Subfamily: Rhacophorinae > Genus: Rhacophorus > Species: Rhacophorus bimaculatus

Leptomantis bimaculata Peters, 1867, Monatsber. Preuss. Akad. Wiss. Berlin, 1867: 32. Syntypes: (2 specimens) ZMB 5681 and NHMW 16091 according to Bauer, Günther, and Klipfel, 1995, in Bauer et al. (eds.), Herpetol. Contr. W.C.H. Peters: 51. Type locality: "Oberlauf des Agusan (Mindanao)" (= Upper Valley of the Agusan), Mindanao, Philippines.

Ixalus ? bimaculatusBoulenger, 1882, Cat. Batr. Sal. Coll. Brit. Mus., Ed. 2: 106.

Philautus bimaculatusStejneger, 1905, Proc. U.S. Natl. Mus., 28: 347. Inger, 1966, Fieldiana, Zool., 52: 344.

Philautus zamboangensis Taylor, 1922, Philipp. J. Sci., 21: 173. Holotype: EHT 1059, by original designation; now CAS 61840 according to Slevin and Leviton, 1956, Proc. California Acad. Sci., Ser. 4, 28: 537. Type locality: "near Pasananka [= Pasonanca], Zamboanga, Mindanao", Philippines. Synonymy by Inger, 1954, Fieldiana, Zool., 33: 399.

Rhacophorus (Philautus) bimaculatusAhl, 1931, Das Tierreich, 55: 52, 64.

Rhacophorus bimaculatusLiem, 1970, Fieldiana, Zool., 57: 100.

Rhacophorus (Leptomantis) bimaculatusDubois, 1987 "1986", Alytes, 5: 76.

Leptomantis bimaculatusIskandar and Colijn, 2000, Treubia, 31: 95.

Rhacohorus bimaculatusHarvey, Pemberton, and Smith, 2002, Herpetol. Monogr., 16: 47, by implication.

English Names

Mindanao Flying Frog (Frank and Ramus, 1995, Compl. Guide Scient. Common Names Amph. Rept. World: 113).

Blue-legged Tree Frog (Kiew, 1987, Malayan Nat. J., 41: 418).

Banded Pigmy Tree Frog (Nutphund, 2001, Amph. Thailand: 157).

Asiatic Tree Frog (Nguyen, Ho, and Nguyen, 2005, Checklist Amph. Rept. Vietnam: 39).

Blue-spotted Tree Frog (Nguyen, Ho, and Nguyen, 2005, Checklist Amph. Rept. Vietnam: 39).


Philippines (Luzon, Bohol, and Mindanao).


See accounts (as Philautus bimaculatus) by Bourret, 1942, Batr. Indochine: 471-472; Inger, 1954, Fieldiana, Zool., 33: 399-401, Taylor, 1962, Univ. Kansas Sci. Bull., 43: 534-536, and Berry, 1975, Amph. Fauna Peninsular Malaysia: 92. See account of Philippine population by Brown and Alcala, 1994, Proc. California Acad. Sci., Ser. 4, 48: 207. See comments under Rhacophorus angulirostris and Rhacophorus cyanopunctatus. See comments by Inger, Orlov, and Darevsky, 1999, Fieldiana, Zool., N.S., 92: 31. Orlov, Lathrop, Murphy, and Ho, 2001, Russ. J. Herpetol., 8: 19, listed this species as part of the Vietnam fauna although on geographic grounds alone this seems unlikely (DRF). Recorded for Thailand and Taylor, 1962, Univ. Kansas Sci. Bull., 43: 487-491, by Khonsue and Thirakhupt, 2001, Nat. Hist. J. Chulalongkorn Univ., 1: 77, these identifications require confirmation. See identification table by Manthey and Grossmann, 1997, Amph. Rept. Südostasiens: 122-123, to compare this species to other rhacophorids of the Sunda Shelf region. Orlov, Murphy, Ananjeva, Ryabov, and Ho, 2002, Russ. J. Herpetol., 9: 97, reported this species from Borneo, but this is apparently due to confusion with Rhacophorus cyanopunctatus (DRF). Nutphund, 2001, Amph. Thailand: 156, provided a brief characterization for Thailand and photograph, which Ohler, 2003, Alytes, 21: 101, attributed to Polypedates sp.Stuart, 2005, Herpetol. Rev., 36: 334-335, suggested that published records of Rhacophorus bimaculatus for Vietnam were based on specimens of Rhacophorus orlovi. See photograph, map, description of geographic range and habitat, and conservation status in Stuart, Hoffmann, Chanson, Cox, Berridge, Ramani, and Young, 2008, Threatened Amph. World: 539. Siler, Welton, Siler, Brown, Bucol, Diesmos, and Brown, 2011, Check List, 7: 182-195, provided a range extension to northern Luzon in Aurora Province, Philippines. Gonzalez, Su, Siler, Barley, Sanguila, Diesmos, and Brown, 2014, Mol. Phylogenet. Evol., 72: 35-41, discussed molecular biogeography. 

External links:

Please note: these links will take you to external websites not affiliated with the American Museum of Natural History. We are not responsible for their content.