When thinking about applying a decorative finish such as coloured render on Ziegel blockwork, it’s important that the materials you are using compliment the substrate (we’ve written previously about failed renders caused by this). Ziegel blocks are known for fire safety, thermal performance and excellent indoor air quality. With that said, the right materials are required in order to compliment the functionality of the substrate and subsequently reduce cracking.
At EWI Store, we have a range of solutions for applying coloured render to high performance blockwork successfully, so let’s take a look at the process and the materials required to ensure crack resistance and a lasting finish.
In order to understand the kind of render that would be best suited for Ziegel, we need to take a look at what exactly Ziegel blocks are and what properties they have. Ziegel blocks are renowned for being high performance because they have excellent insulating capabilities.
Their high thermal performance is due to the air channels that run vertically through each block creating a honeycomb effect, while the clay itself has more air pockets made by sawdust that is burned off in the kiln during the firing process. Ziegel blocks are also a breathable building material as they can maintain the equilibrium of humidity by storing and releasing heat and moisture, helping to maintain room comfort and healthy indoor air quality all year round.
Ziegel are also a highly dense material, creating a uniform substrate that offers reduced thermal bridging with a quick and easy construction process. Although Ziegel is a high performance block, it does need finishing with a protective layer to prevent weathering. This is where coloured render systems are ideal, because the technology of the system means that the substrates functionality is in no way hindered by the coloured render, instead the materials that go into the render system compliment the substrate.
Ziegel block creates a uniform, continuous substrate which is incredibly easy to render in terms of creating a smooth surface; the only area that requires close attention is using the right materials and the right method of application. You can decide based on the climate and weather conditions whether or not you need to apply a two-coat system or a three-coat render system for this kind of blockwork. The default for the UK tends to be the three-coat system because the Lightweight Basecoat and render on its own will not withstand the weather conditions.
The two-coat system consists of the application of the Lightweight Basecoat, then a tightcoat and then a render.
In a typical render system on an ordinary substrate, a substrate primer would be necessary to limit the absorptive capacity of the substrate. However, when rendering a Ziegel substrate, to limit the absorptive capacity of the substrate you do not need to prime. Instead, you spray apply a first pass of the Lightweight basecoat at approximately two thirds of the thickness it should be applied at – around 12mm. You leave this to ‘pull back’ and dry slightly before appyling the final one third to take the basecoat up to its total thickness.
The Lightweight Basecoat needs to be left for a period 0f 24-48 hours to dry, then the tightcoat is applied. This consists of another thin layer of the Lightweight Basecoat; it is applied to the dried basecoat and is sponged or rubbed up to achieve the required texture. Once the tightcoat has been applied, it can be primed and painted or primed and rendered using a ready-mix render (e.g. Silicone or Silicone Silicate). You can also use Mineral Render (and then paint with Silicone Paint) or you can use Monocouche render. The main thing here is that the tightcoat must be primed if you are using a ready-mix render such as Silicone or Silicone Silicate, because otherwise blooming may occur across the lime basecoat.
A three-coat system is the standard system that is recommended for use in the UK. The three coat system involves applying the Lightweight Basecoat in two passes, as outlined above. Once the Lightweight Basecoat has cured (after 24-48 hours), a layer of the Premium Adhesive with Fibreglass Mesh embedded is then applied on top. The Premium Adhesive is then primed using a render primer, before the render of your choice is applied; whether it’s Silicone, Silicone Silicate, Mineral or Monocouche.
The reason that the Premium Adhesive is applied as an extra layer is because it is far stronger than the Lightweight Basecoat, and when applied with a Fibreglass Mesh embedded within the adhesive it provides the required tensile strength to be able to withstand harsh weather conditions without cracking.
When applying coloured render to a Ziegel substrate, we really recommend the use of Silicone Render as it’s incredibly flexible, breathable and hydrophobic. It will therefore resist any cracking, prevent water ingress and allow water vapour to escape from the building fabric. It’s currently our most high performance coloured render and is an extremely versatile and popular solution for a wide range of substrates.
Silicone Render can also be tinted to create any shade of colour (hence the name coloured render). If coloured render is of interest to you, you can view our full shade range using our render colour chart, or you can purchase a coloured render sample pot.
For any further questions about applying render to Ziegel block, contact our technical team or leave a comment down below – we are always happy to help!
We upload a new blog post every Tuesday and Thursday, so stay tuned for more content!
Applying coloured render onto ICF
Applying coloured render to thermalite blocks
Replacing pebbledash with coloured render
Applying render to a timber framed property
Applying coloured render to render carrier board
Cookie | Duration | Description |
---|---|---|
__stripe_mid | 1 year | This cookie is set by Stripe payment gateway. This cookie is used to enable payment on the website without storing any patment information on a server. |
__stripe_sid | 30 minutes | This cookie is set by Stripe payment gateway. This cookie is used to enable payment on the website without storing any patment information on a server. |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
apbct_cookies_test | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_page_hits | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_prev_referer | session | Functional cookie placed by CleanTalk Spam Protect to store referring IDs and prevent unauthorized spam from being sent from the website. |
apbct_site_landing_ts | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_site_referer | 3 days | This cookie is placed by CleanTalk Spam Protect to prevent spam and to store the referrer page address which led the user to the website. |
apbct_timestamp | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_urls | 3 days | This cookie is placed by CleanTalk Spam Protect to prevent spam and to store the addresses (urls) visited on the website. |
AWSALBCORS | 7 days | This cookie is managed by Amazon Web Services and is used for load balancing. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
ct_checkjs | session | CleanTalk–Used to prevent spam on our comments and forms and acts as a complete anti-spam solution and firewall for this site. |
ct_fkp_timestamp | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_pointer_data | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_ps_timestamp | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_sfw_pass_key | 1 month | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
ct_timezone | session | CleanTalk–Used to prevent spam on our comments and forms and acts as a complete anti-spam solution and firewall for this site. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__zlcmid | 1 year | This cookie is used by Zendesk live chat and is used to store the live chat ID. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
__utma | 2 years | This cookie is set by Google Analytics and is used to distinguish users and sessions. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 minutes | Google Analytics sets this cookie, to determine new sessions/visits. __utmb cookie is created when the JavaScript library executes and there are no existing __utma cookies. It is updated every time data is sent to Google Analytics. |
__utmc | session | The cookie is set by Google Analytics and is deleted when the user closes the browser. It is used to enable interoperability with urchin.js, which is an older version of Google Analytics and is used in conjunction with the __utmb cookie to determine new sessions/visits. |
__utmt | 10 minutes | Google Analytics sets this cookie to inhibit request rate. |
__utmv | 2 years | The __utmv cookie is set on the user's device, to enable Google Analytics to classify the visitor. |
__utmz | 6 months | Google Analytics sets this cookie to store the traffic source or campaign by which the visitor reached the site. |
sib_cuid | 6 months | Purechat uses this cookie to send data to purechat.com, to connect visitors to the reservation team and track visitors to stay on portal. |
SRM_B | 1 year 24 days | Used by Microsoft Advertising as a unique ID for visitors. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_gtag_UA_61069204_2 | 1 minute | Set by Google to distinguish users. |
_gat_UA-61069204-2 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
ANONCHK | 10 minutes | The ANONCHK cookie, set by Bing, is used to store a user's session ID and also verify the clicks from ads on the Bing search engine. The cookie helps in reporting and personalization as well. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
NID | 6 months | NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
uuid | 6 months | MediaMath sets this cookie to avoid the same ads from being shown repeatedly and for relevant advertising. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_clck | 1 year | No description |
_clsk | 1 day | No description |
_uetvid | 1 year 24 days | No description available. |
AnalyticsSyncHistory | 1 month | No description |
apbct_pixel_url | session | No description |
apbct_visible_fields_0 | session | No description |
apbct_visible_fields_1 | session | No description |
apbct_visible_fields_10 | session | No description |
apbct_visible_fields_2 | session | No description |
apbct_visible_fields_3 | session | No description |
apbct_visible_fields_4 | session | No description |
apbct_visible_fields_5 | session | No description |
apbct_visible_fields_6 | session | No description |
apbct_visible_fields_7 | session | No description |
apbct_visible_fields_8 | session | No description |
apbct_visible_fields_9 | session | No description |
ct_checked_emails | session | No description |
ct_has_scrolled | session | No description |
ct_mouse_moved | session | No description |
ct_screen_info | session | No description |
ictf_master | never | No description available. |
li_gc | 2 years | No description |
m | 2 years | No description available. |
SM | session | No description available. |
testinfinitycookie | session | No description |
woocommerce_show_tax | 7 days | No description available. |
wp_woocommerce_session_c5ac76b408021294cb56bcc27eddf8a1 | 2 days | No description |