| CODE | DESCRIPTION | SIZE | WEIGHT gr/m2 | FORMAT |
| 3A173708 | Gridlok Excel (Green) | 475mm x 475mm | 1.05 kg | Panels |

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woosidebars domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/web/site/public_html/wp-includes/functions.php on line 6121
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/plugins/super-forms/add-ons/super-forms-csv-attachment/super-forms-csv-attachment.php on line 277
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/helpers/helpers-frontend.php on line 31
Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/structure/structure-header.php on line 82
Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/structure/structure-header.php on line 202
Deprecated: Optional parameter $content declared before required parameter $code is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/accordion.php on line 3
Deprecated: Optional parameter $content declared before required parameter $code is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/accordion.php on line 17
Deprecated: Optional parameter $content declared before required parameter $tag is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/tabs.php on line 3
Deprecated: Optional parameter $content declared before required parameter $tag is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/blog_posts.php on line 3
Deprecated: Optional parameter $content declared before required parameter $code is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/google_maps.php on line 3
Deprecated: Optional parameter $content declared before required parameter $code is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/item_list.php on line 4
Deprecated: Optional parameter $content declared before required parameter $code is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/item_list.php on line 13
Deprecated: Optional parameter $content declared before required parameter $tag is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/portfolio.php on line 4
Deprecated: Optional parameter $content declared before required parameter $tag is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/ux_products.php on line 4
Deprecated: Optional parameter $content declared before required parameter $tag is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/ux_products_list.php on line 4
Deprecated: Optional parameter $content declared before required parameter $tag is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/product_flip.php on line 4
Deprecated: Optional parameter $content declared before required parameter $tag is implicitly treated as a required parameter in /var/web/site/public_html/wp-content/themes/flatsome/inc/shortcodes/product_categories.php on line 4
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/breakpoints.php on line 100
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/breakpoints.php on line 163
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/breakpoints.php on line 164
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/breakpoints.php on line 173
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/breakpoints.php on line 212
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/breakpoints.php on line 240
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/breakpoints.php on line 267
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/urls.php on line 32
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/web/site/public_html/wp-content/themes/flatsome/inc/builder/core/server/helpers/urls.php on line 33
Deprecated: Creation of dynamic property DUP_PRO_Global_Entity::$notices is deprecated in /var/web/site/public_html/wp-content/plugins/duplicator-pro/classes/entities/class.json.entity.base.php on line 243
Deprecated: Creation of dynamic property DUP_PRO_Global_Entity::$package_scan_mode is deprecated in /var/web/site/public_html/wp-content/plugins/duplicator-pro/classes/entities/class.json.entity.base.php on line 243
Deprecated: Creation of dynamic property DUP_PRO_Global_Entity::$package_scan_size is deprecated in /var/web/site/public_html/wp-content/plugins/duplicator-pro/classes/entities/class.json.entity.base.php on line 243
The Gridlok Excel gravel pavers are all SUDs compliant (Sustainable Urban Drainage Systems) and do not require planning permission for applications such as carparks, overflow parking, access roads, pathways, golf buggy paths, light aircraft taxiways, cycle paths, etc.
The product can withstand loads of 300 tonnes per square metre, and each paver is 475MM x 475MM (4.4 pavers per square metre) and 39MM in depth. The Gridlok Excel Porous paver is manufactured from 100% recycled polypropylene/polyethylene, and is suitable for grass reinforcement or gravel retention applications.
Porous Paver Installation
Gridlok®
Paver installation – in all cases, before installing MESH4 porous pavers you should first determine the ground conditions over which the paver is to be installed. Ideally, you should consult with a specialist to provide a CBR (Californian Bearing Ratio) test. The CBR result will give an indication of the required sub base.
During construction, care of the ground to be infiltrated should be taken. The fines content of the sub base should be controlled, so where possible, store the stone off site and construct the porous surfaces as late in the project as possible to prevent clogging and compaction. The sub base should be DOT type 3 and construction should be in accordance with BS 7533: Part 3: 1997 Code of Practice for laying pre cast concrete paving blocks and clay pavers for flexible pavements.
For gravel finishes
A geotextile should be laid over the sub base below the pavers, to prevent the cross contamination of the gravel. Once placed on the geotextile, the pavers should be filled using a 6/10mm clean angular gravel. Once filled, the pavement can be used immediately.
For grass finishes
the sub base should be mixed with 30% sharp sand. Once the pavers are placed on the sub base, they should then be filled with a mix of 70% sharp sand with 30% soil and seeded with grass seed. Once seeded, the pavement should be left un-trafficked to allow for the grass to establish. Alternatively, turf can be laid directly on top of the filled pavers. Once the turf has been laid, it will need to be rolled and left for at least two mowing cycles to allow for the roots to establish.
*Note: the depth of sub base may be reduced by including a ground stablising mesh geogrid.
Contact our ground reinforcement team on 01978 807345 for further information.
The paver will self-stabilise over a period of time due to the injection moulded studs at the base of the paver. This will also prevent any lateral movement over time.
Because of the open nature of the cellular structure of the pavers, grass roots allow water and nutrients to drain easily and form good root growth if the intended application is to have a finished natural looking grass structure.
Contact the team at Mesh4 today for more information on our plastic/gravel driveway grid systems.
Be the first to review “GridLok Excel Gravel Pavers”
You must be logged in to post a review.