The author did not fashion completed entries with his package. There was no need and its just too many ID entries to be bothered with anyway for such generous offerings. Instead, he elected to let the users construct their own runway numbers and ID entries, while he provides the coordinates and other pertinent miscellany for each base.
So to answer your question, there are no correct runway numbers and ID's for his works. You just plug them into the end of your current airbase.dat and ID them as you see fit. But the actual runway numbers sequence has to start where your current list ends (Gasmata is the last entry in the stock list):
[runway.123]
id=8050
name=Gasmata
base_lat=S6 15.77
base_lon=E150 20.22
base_alt=0
heading=223
allegiance=0
units_across=2
takeoff_start_pos=-400,0
takeoff_stop_pos=1600,200
landing_start_pos=5000,350
landing_touchdown_pos=500,0
landing_stop_pos=-250,0
[runway.124] <<< VERY IMPORTANT TO SEQUENCE THIS NUMBER CORRECTLY
id=8051 *** SEQUENCE NOT IMPORTANT HERE, BUT USEFUL ***
name=Denpassar
base_lat=S08 42.15
base_lon=E115 12.78
base_alt=3
heading=120
allegiance=0
units_across=2
takeoff_start_pos=-000,0
takeoff_stop_pos=1325,200
landing_start_pos=5000,350
landing_touchdown_pos=550,0
landing_stop_pos=-250,0
***NOTE: If the ID number is taken by another add-on base used in a mission, you'll have CTD issues when loading the mission. This is always a major concern as you continue to build your scenery library and you'll need to pay close attention to this detail going forward. Most scenery designers follow the same pattern as the author of this eawwii_full package by allowing the users to assign their own ID's. But occasionally you will download a scenery package with base ID numbers already assigned for use in a designed mission package.
