菱生精密工業股份有限公司 2013 Sustainability Report
This company has a newer report for 2025.View the latest report
- Reporting Year
- 2013
- Disclosure Period
- 2013/01/01 ~ 2013/12/31
- Industry
- 半導體業
- Verification Body
- Not disclosed
- Reporting framework
- GRI(G3.1)
Report summary
- This page summarizes the 2013 sustainability report and ESG report PDF source for 菱生精密工業股份有限公司 (2369).
- The reporting period is 2013/01/01 to 2013/12/31, in the 半導體業 industry.
- No third-party verification or assurance provider is listed yet. Use this page to check the report’s verification, assurance, and disclosure standards.
- Compare public disclosure approaches across prior-year and peer reports. Your company’s actual disclosures must still be based on its own data and supporting evidence.
Report details
- Company
- 菱生精密工業股份有限公司(2369)
- Reporting Year
- 2013
- Disclosure Period
- 2013/01/01 to 2013/12/31
- Industry
- 半導體業
- Third-party information
- No third-party verification or assurance provider information is currently listed.
- PDF source
- The original ESG report PDF can be downloaded or opened from this page
2013 ESG Metrics and Industry Comparison
No ESG open data metrics are currently available.
How to use this report
- Compare how 菱生精密工業股份有限公司 structured 半導體業 sustainability report chapters and material topics in 2013.
- Confirm the reporting period, listed third-party verification or assurance provider information, and the downloadable ESG report PDF source.
- Mark public disclosures and original page numbers that can be referenced as research materials for planning chapters and indicators for your own company.
Reports from the Same Industry
半導體業2013
How to use this public report as a reference
Compare sections, indicators, and disclosure approaches, and go back to the original page numbers for context. Peer content does not reflect your own company's facts; actual disclosures should still be based on your company's data and supporting documents.
The report has opened in a new tab
Next, you can:
AI chat is temporarily unavailable. Please try again.