How close are the quaterly reported results to the yearly ones (for KGHM)

Companies publish their results every quarter. These results are often a good indication how a company will perform in the year (if Q'1 data for 2012 are better than the Q'1 from 2011, that's generally a good sign). The Q'4 report is also published much earlier that the yearly report for a company, at least in Poland the gap can be a few months. So the question is do the combined Q'1-Q'4 results represent in essence the same information, as results published in the yearly report for which one has to wait, could one use the information in the summed Q'1-Q'4 reports to derive at least a good estimate of the yearly results?

So here is a data for KGHM


Table 1. Income (after tax) for KGHM with quarterly report data summed up for each year (YR and QT are the consolidated yearly and quarterly results; both are given in thousands of PLN)

YearYR Q'1-Q'4 
(sum)		Fractional
difference
2001-838,625-830,9430.009
2002-214,734-216,299-0.007
2003673,043661,3160.017
20041,376,7151,357,8920.014
20052,102,3322,117,130-0.007
20063,479,1833,532,132-0.015
20073,934,5593,961,014-0.007
20082,766,1792,766,1790.000
20092,327,9932,327,9930.000
20104,724,5074,714,2210.002
201111,063,45611,078,034-0.001
Average (of absolute value of fractional difference)0.007

In other words, the sum of quarterly reports seems to be a good proxy for the yearly result (as it should be!), at least in the case of KGHM. The next question could be to see if that's the case for all the companies on WIG. KGHM is admittedly one of the largest/most prominent players (part of the WIG20) so it was unlikely that it would fail this check. Also, is the agreement between yearly and quarterly data true for measures other than income (discrepancies in which would attract most attention)?

The second part of the story was looking at the whole WIG20 index

Company code Percentage difference of 
YT to sum(Q1-Q4)
PLTAURN00011 108.5
PLDWORY00019 9.1
PLBH00000012 0.8
LU0327357389 130.9
PLTLKPL00017 0.6
PLPZU0000011 0.0
PLPKO0000016 17.7
PLPEKAO00016 0.1
PLGTC0000037 1.1
PLSOFTB00016 -0.8
PLBRSZW00011 -3.6
PLPKN0000018 -3.3
PLPGNIG00014 5.5
PLLOTOS00025 5.3
PLKGHM000017 0.1
PLBRE0000012 2.0
PLLWBGD00016 12.5
PLTVN0000017 33.7
PLPGER000010 23.6
PLJSW0000015 0.0

The meaning of the percentage difference is the following: if it's zero (or close to) than the quarterly results and the yearly results are identical (or almost). If it's above zero, the quarterly reports under-reported the earnings; conversely and vice-versa.

The source code and how to reproduce this example are in
Part 1: https://github.com/jandom/FinAnalysis/commit/37fb8673c3651298a120627fc0a5c2705027066f

Comments

Post a Comment

Popular posts from this blog

React.js – edit and delete comments in CommentBox

It appears customary for high-intelligence, high-skills groups of engineers to "roll their own" whenever they have a chance to. Counter-intuitively to most managerial/MBA types out there, re-inventing the wheel can give you... a better wheel. Success is not guaranteed though – but these people may leave sooner rather than later if you don't let them... Having looked at number of JS frameworks (ember, backbone, angular) there was no clear winner. They were all a mess, at least to me. So I approached React.js with no hopes – how much better could it possible be? It turns out, a lot! This post will be an extension of the official React.js tutorial . The tutorial stops at the stage where you can add comments to a dynamic lists, that will grow as you add comments. This falls short of the functionality displayed on facebook: once you add a comment you can edit or delete it, so that's what're going to do. Full disclosure, I only started using React this weekendo so m
Read more

Example slurm cluster on your laptop (multiple VMs via vagrant)

To anybody who's considering a switch to modern queuing systems, like slurm, this will be an useful guide. Rather than doing a roll out on production nodes, we'll try things out in vagrant. This text assumes you have vagrant installed on your local machine (it's very easy). The ultimate aim will be to setup 2 servers (worker nodes) and one master/controller, and run a simple job on them. There are multiple great guides out there: most of them are out of date, and won't work without some tweaking on Ubuntu 16.04 Xenial. The entirety of the code is hosted at https://github.com/jandom/gromacs-slurm-openmpi-vagrant The README.md file will show you how to set it up, with checks on every step. References https://mussolblog.wordpress.com/2013/07/17/setting-up-a-testing-slurm-cluster/ https://github.com/gabrieleiannetti/slurm_cluster_wiki/wiki/Installing-a-Slurm-Cluster http://philipwfowler.me/2016/04/14/how-to-setup-a-gramble/ https://github.com/dakl/slurm-clus
Read more

Wrapping openbabel in python - using cython

The previous post showed a contrived example of how one could access the openbabel functionality in python using the boost libraries. There is alternative to boost to wrap around c/c++ code, it's called cython. Here is an example openbabel wrapper, exposing some very simple functionality. Just before diving in, you should know that there already exists a wrapper around openbabel in python (it is called pybel). What I'm showing here doesn't even come close to pybel in terms of usefulness, the idea here is to show a demo of how easy wrapping things in python is. #! /usr/bin/python from ez_setup import use_setuptools use_setuptools() from setuptools import setup, Extension, find_packages from Cython.Distutils import build_ext import sys, os import glob import subprocess as sub def get_include(name="openbabel"): p = sub.Popen('locate %s' % name ,stdout=sub.PIPE,stderr=sub.PIPE, shell=True) output, errors = p.communicate()
Read more