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
            nav
            navPerShare
            opexOfNav
            quarterlySharePrice
          }
          estimates {
            year
            quarter
            revenue
            revenueGrowth
            ebitAdjusted
            ebitReported
            ebitda
            enterpriseValue
            epsAdjusted
            dividend
            dividendYield
            sharePrice
            nav
            navPerShare
            opexOfNav
            quarterlySharePrice
          }
        }
      }
      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
    }
  }
}


__typename

title

isPremium

lang

htmlBody

summary

companies

createdAt

publishers

authors

reactionGroups

pageUrl

translations

imgUrl

description

Analyst

Erkki Vesola

Wärtsilä specializes in power solutions for the marine and energy sectors. The business is managed based on several business segments and the range includes integrated system solutions, spare parts, and associated service functions during the installation cycle, but also complete operation and optimization services. The company was originally founded in 1834 and is headquartered in Helsinki, Finland.

News Powered by Cision              Wärtsilä suunnittelee muutoksia taloushallinnon organisaatioonsa toimintansa...    Wärtsilä Oyj, Lehdistötiedote 3. maaliskuuta 2026 klo 10.00 Teknologiayhtiö Wärtsilä suunnittelee                             Technology company Wärtsilä is planning structural changes to its global finance organization. The aim of the changes is to increase operational efficiency, strengthen expertise, and ensure the company’s global competitiveness and strong position for long-term growth. As part of the plans, Wärtsilä intends to reorganize and right-size its finance functions and establish an internal service center in Gdańsk, Poland. This service center would complement the expertise of the corresponding center located in Vaasa. As the plans may lead to a reduction in finance positions, Wärtsilä is initiating change negotiations regarding its finance organization. The estimated reduction need is a maximum of 205 positions globally, of which approximately 110 are in Finland. Simultaneously, there are plans to create approximately 130 new positions, about 30 of which would be in Finland. The number of new positions as well as potential redundancies and other alternative measures will be confirmed during the change negotiations.

Yahoo Finance news = Reuters news today (https://www.reuters.com/sustainability/climate-energy/wartsila-ceo-eyes-boost-trump-datacenter-push-2026-02-27/) Also interesting in that news is the mention that next Wednesday (March 4) there is a meeting at the White House where companies building data centers are expected to commit to increasing electricity production.

Yahoo Finance              Wartsila Secures 1.2 GW US Data Center Orders as Turbines Sell Out    The Finnish power equipment maker wins three large US gas-engine contracts amid AI-driven power demand and tight turbine supply.                             An article about Wärtsilä and the potential to win more data center deals in the US.

There is quite a discrepancy between Wärtsilä’s recommendations, current pricing, and other companies operating in the data center construction sector. Wärtsilä’s and Siemens Energy’s stock price charts over the past year are virtually identical and firmly on an upward trajectory. Wärtsilä’s recommendation on Nordnet, for example, is essentially to dump it quickly, with a target price around €25. Conversely, SE’s recommendation is a strong buy, with an upside of about 25%.

It looks like there will be a larger piece on Wärtsilä regarding the data center theme in tomorrow’s Helsingin Sanomat. Published online about an hour ago (paywall): Wärtsilästä tuli yllättävä tekoälymenestyjä | HS.fi A couple of quotes:  ”In the United States, a large portion of the planned data centers intend to produce their electricity in their own gas power plants, as the waiting time for grid connections has stretched to an average of eight years.” …  ”Demand for Wärtsilä’s engines for data center use is only just waking up. According to Agnevall, mainly because their excellence is not well known.”

Because… well, uh, look at the picture. From one data center project, I saw that the power distribution to the server racks was done in blocks. Power was always supplied to a couple of rows of server racks through an electrical switchboard installed in a container like that. I don’t remember for sure if, under normal conditions, one transformer fed one such electrical container or if the supply arrangements were somehow different. However, for each such electrical container, there was a dedicated generator container to back up the supply for that specific electrical container. In that facility, there were more than a dozen of those server row-electrical container-genset container blocks, and the power levels were probably in the 1-2 MW per block range. So, that large number of backup generators is due to this modular block approach that these data centers seem to favor. The facility is easy to scale when everything is modular and built from specific pieces. With a total capacity of 885 MW and that number of backup generators, the power per block would be around 1.8 or 2.5 MW, which would sound reasonable. Additionally, from a maintenance and availability standpoint, such smaller units are surely a better option than one larger machine that would supply multiple blocks at once.

Quite a large number of small gensets. Why is that?  Wouldn’t a smaller number of larger ones make more sense? Even so, for a total capacity of 885 megawatts, more than 40 of Wärtsilä’s largest four-stroke engines are needed.

Wärtsilä

Wärtsilä's Q4'23 pre-silent period conference call offered no significant news, but the business has progressed as expected, and especially our confidence in the good development of the service business strengthened.

<p>Wärtsilä's Q4'23 pre-silent period conference call offered no significant news, but the business has progressed as expected, and especially our confidence in the good development of the service business strengthened. We raised our profitability forecasts moderately and there is still a reasonable upside in the stock. </p> 

	2022	23e	24e
Revenue	5,843.0	6,160.1	7,394.3
growth-%	22.3 %	5.4 %	20.0 %
EBIT (adj.)	324.0	505.3	690.2
EBIT-% (adj.)	5.5 %	8.2 %	9.3 %
EPS (adj.)	0.47	0.54	0.79
Dividend	0.26	0.40	0.50
Dividend %	3.3 %	1.2 %	1.4 %
P/E (adj.)	16.7	64.6	43.8
EV/EBITDA	21.7	33.0	24.0

Wärtsilä: Keep your eyes on the horizon

Key Estimate Figures2024-01-04

Forum discussions