contentSlug

type

ContentSlug_ContentQuery

slug

ContentPageContentQuery

content

trendingContent

query ContentSlug_ContentQuery(
  $contentSlug: String!
  $type: [ContentType!]
) {
  ...ContentPageContentQuery_13QmVO
}

fragment CompanyDetails_Content on Content {
  __isContent: __typename
  companies {
    name
    description
    pageUrl
    id
  }
}

fragment ContentBasicInfo on Content {
  __isContent: __typename
  id
  type
  title
  lang
  companies {
    viewerIsFollowing
    id
    name
    pageUrl
  }
  tags {
    viewerIsFollowing
    id
    name
    pageUrl
  }
  ...PublishingDetails
  ...Reactions
}

fragment ContentMetadata on Content {
  __isContent: __typename
  type
  title
  lang
  pageUrl
  alternatePageUrls: translations {
    __typename
    pageUrl
    lang
  }
  imgUrl
  description
  ... on Video {
    liveTime
    videoUrl
  }
  ... on Webcast {
    liveTime
    videoUrl
  }
}

fragment ContentPageContentQuery_13QmVO on Query {
  content(slug: $contentSlug, type: $type) {
    __typename
    id
    type
    title
    isPremium
    lang
    htmlBody
    summary
    companies {
      forum {
        latestPosts {
          ...ForumPosts
        }
      }
      name
      id
      viewerIsFollowing
      pageUrl
      defaultInstrument {
        isin
        id
        marketOpen
        marketClose
        marketplace {
          region
        }
        returns {
          total
        }
      }
    }
    tags {
      viewerIsFollowing
      id
      name
      pageUrl
    }
    createdAt
    ... on Video {
      liveTime
    }
    ... on Webcast {
      liveTime
    }
    slug
    ... on CompanyReport {
      reportUrl
    }
    ... on ThirdPartyCompanyReport {
      reportUrl
    }
    ... on StockExchangeRelease {
      reportUrl
    }
    ...ContentBasicInfo
    ...ContentMetadata
    ...PriceAndRecommendation_Content
    ...CompanyDetails_Content
    ...ReportLink_Content
    ...KeyFigures_Content
  }
  ...TrendingContent_1jQ2Cn
}

fragment ForumPosts on ForumPost {
  text
  likesCount
  url
  author
  postedAt
  authorImgUrl
}

fragment KeyFigures_Content on Content {
  __isContent: __typename
  companies {
    defaultInstrument {
      estimateData {
        modelType
        reportingCurrency
      }
      snapshot {
        transaction {
          date
          actualized {
            year
            quarter
            revenue
            revenueGrowth
            ebitAdjusted
            ebitReported
            ebitda
            enterpriseValue
            epsAdjusted
            dividend
            dividendYield
            sharePrice
          }
          estimates {
            year
            quarter
            revenue
            revenueGrowth
            ebitAdjusted
            ebitReported
            ebitda
            enterpriseValue
            epsAdjusted
            dividend
            dividendYield
            sharePrice
          }
        }
      }
      id
    }
    id
  }
}

fragment PriceAndRecommendation_Content on Content {
  __isContent: __typename
  createdAt
  companies {
    name
    pageUrl
    defaultInstrument {
      priceData {
        tradeCurrency
      }
      snapshot {
        priceData {
          date
          lastPrice
          tradeCurrency
        }
        transaction {
          date
          recommendation
          targetPrice
        }
        prevTransaction {
          recommendation
        }
      }
      id
    }
    id
  }
}

fragment PublishingDetails on Content {
  __isContent: __typename
  createdAt
  publishers {
    name
    imgUrl
  }
  authors {
    __typename
    id
    name
    slug
    imgUrl
    jobTitle
  }
  ... on Video {
    liveTime
  }
  ... on Webcast {
    liveTime
  }
}

fragment Reactions on Content {
  __isContent: __typename
  id
  reactionGroups {
    reactionType
    reactionsCount
    viewerReacted
  }
}

fragment ReportLink_Content on Content {
  __isContent: __typename
  type
  isPremium
  ... on CompanyReport {
    reportUrl
  }
  ... on ThirdPartyCompanyReport {
    reportUrl
  }
  ... on StockExchangeRelease {
    reportUrl
  }
}

fragment TrendingContent_1jQ2Cn on Query {
  trendingContent(type: ARTICLE) {
    __typename
    id
    title
    lang
    pageUrl
    createdAt
    type
    imgUrl
    companies {
      squareLogoUrl
      name
      id
    }
    authors {
      __typename
      imgUrl
      id
    }
    publishers {
      imgUrl
    }
  }
}


sisapiiritieto-siili-solutions-oyj-alentaa-vuoden-2025-oikaistua-ebitaa-koskevaa-ohjeistustaan

__typename

title

isPremium

lang

htmlBody

summary

companies

createdAt

publishers

authors

reactionGroups

pageUrl

translations

imgUrl

description

Siili Solutions operates in the IT sector. The company develops and integrates software for information systems, and offers services related to the development of technology platforms, information management, IT architecture, and various project management. The expertise is found in data management, analysis, and artificial intelligence. The company was founded in 2005 and is headquartered in Helsinki.

Hey, yeah, I also contacted the company about this, and it’s clearly explained in the English announcement

On the one hand, I see that the company would have exceeded the market’s expectations baked into the share price by hitting the lower end of its guidance, and that, regarding Q4 business, it could very well be de facto happening, corrected from a “technical error.” On the other hand, my trust in the company’s communication has generally been tested for a long time, and this kind of mess doesn’t increase it much. So I don’t just mean the error (let it pass), but the fact that one has to guess which press release to read and how. One can talk vague nonsense about AI, which isn’t true, or even a lie, in a promotional sense, but in financial reporting, you don’

That’s what you get for leaving communications in the capable hands of Siili AI  In itself, the Finnish and English versions are not contradictory; the English one is just more precise.

Indeed, the English announcement was much clearer than the Finnish one, meaning it hasn’t been corrected, and part of the guidance calculation is explained by that technical error. If the magnitude is what Frans is guessing, then a negative surprise is almost a positive one compared to expectations. SEB also reached the same conclusion as Frans, but couldn

So, the English announcement has different information than the Finnish announcement. That doesn’t really clarify the matter. The Finnish one didn’t mention that correction affecting adjusted EBITA, but rather the result. “The 2025 result will also be significantly burdened by the correction of a technical accounting error” Don’t know what the situation is then, strangely confusing vibe.

Inderes              Inside information: Siili Solutions Plc lowers its financial guidance for...    Inside information: Siili Solutions Plc lowers its financial guidance for 2025 adjusted EBITA Siili Solutions Plc Insider information 2 December 2025 at 15:55 EET Siili Solutions Plc lowers ...                             “During the autumn Siili’s sales has developed positively. However, some customers have postponed their investment decisions until next year. The group adjusted EBITA for 2025 will also be significantly affected by the correction of a technical accounting error.” edit:AI näköjään kääntää englanninkielisen lainauksen suomeksi inden palstalla, mutta linkin takaa löytyy

Hi @Frans-Mikael_Rostedt Did you ask Siili about that, or what logic led you to the conclusion from the release that this technical entry would partly explain the negative result, and would not come as bad news in addition to it?

Siili Solutions

Sisäpiiritieto: Siili Solutions Oyj alentaa vuoden 2025 oikaistua EBITAa koskevaa ohjeistustaan Siili Solutions Oyj Sisäpiiritieto 2.12.2025 kello 15.55 Siili Solutions Oyj alentaa vuoden 2025...

Sisäpiiritieto: Siili Solutions Oyj alentaa vuoden 2025 oikaistua EBITAa koskevaa ohjeistustaan Siili Solutions Oyj Sisäpiiritieto 2.12.2025 kello 15.55 Siili Solutions Oyj alentaa vuoden 2025 oikaistua EBITAa koskevaa tulosohjeistustaan. Yhtiö arvioi koko vuoden oikaistun EBITAn olevan 3,9-4,5 miljoonaa euroa (aiempi ohjeistus 4,7-7,7 miljoonaa euroa). Siilin vuoden 2025 liikevaihtoa koskeva ohjeistus säilyy ennallaan (108-130 miljoonaa euroa). Syksyn kuluessa Siilin myynti on kehittynyt positiivisesti, mutta osa Siilin asiakkaista on siirtänyt investointipäätöksiään ensi vuoden puolelle. Vuoden 2025 tulosta tulee lisäksi merkittävästi rasittamaan teknisen kirjanpidollisen virheen oikaiseminen. Uusi ohjeistus vuodelle 2025:&nbsp; Vuoden 2025 liikevaihdon arvioidaan olevan 108-130 miljoonaa euroa ja oikaistun EBITAn 3,9-4,5 miljoonaa euroa&nbsp; Aiempi ohjeistus vuodelle 2025:&nbsp; Vuoden 2025 liikevaihdon arvioidaan olevan 108-130 miljoonaa euroa ja oikaistun EBITAn 4,7-7,7 miljoonaa euroa.&nbsp; Yhtiö julkistaa vuoden 2025 tilinpäätöstiedotteen 11.2.2026. Lisätietoja:&nbsp; Toimitusjohtaja Tomi Pienimäki&nbsp; Puhelin: 040 834 1399, sähköposti: tomi.pienimaki(at)siili.com&nbsp; Talousjohtaja Tuomas Toropainen&nbsp; Puhelin: 050 911 9598, sähköposti: tuomas.toropainen(at)siili.com&nbsp; Jakelu:&nbsp; Nasdaq Helsinki Oy&nbsp; Keskeiset tiedotusvälineet&nbsp; www.siili.com/fi&nbsp; Siili Solutions Oyj lyhyesti:&nbsp; Siili Solutions Oyj on tekoälyavusteisen ohjelmistokehityksen edelläkävijä. Siili on asiakkaalle paras kumppani, kun haetaan kasvua, tehokkuutta ja kilpailuetua digitaalisin keinoin. Päämarkkinamme ovat Suomi, Alankomaat Iso-Britannia ja Saksa. Siili Solutions Oyj:n osakkeet noteerataan Nasdaq Helsinki Oy:n pörssilistalla. Siili on kasvanut kannattavasti perustamisestaan vuodesta 2005 lähtien. www.siili.com/fi&nbsp; <img src="https://www.globenewswire.com/newsroom/ti?nf=MTAwMTE0MjQxOSM0MDIyNzU4MDQjMjA5NTE5NQ==" alt=""> <img src="https://ml-eu.globenewswire.com/media/YTYwOTZlOGMtZDAxNy00Mzg1LTlkOWYtYTJiN2UyNjM1OWI1LTExMDY3NjYtMjAyNS0xMi0wMi1maQ==/tiny/Siili-Solutions-Oyj.png" alt="">