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
    }
  }
}


tecnotree-announces-follow-up-agreement-with-tier-1-customer

__typename

title

isPremium

lang

htmlBody

summary

companies

createdAt

publishers

authors

reactionGroups

pageUrl

translations

imgUrl

description

Analyst

Joni Grönqvist

Tecnotree operates in the IT sector. The company specializes in the development of digital communication solutions. The services include, for example, business process services and subscription management for corporate customers in telecom and other digital service providers. Operations are held on a global level, with the largest presence in Asia, Africa and the Middle East.

Based on that, one might think so. But that’s what was thought about Kakkonen at first too, until his mind changed… I don’t have access to the original article, but as I understand it, it doesn’t state directly that the takeover bid won’t be accepted? They just keep complaining about an “opportunistic offer”… If Nieminen wants other shareholders to join the “collective effort,” i.e., to refrain from the offer, he could just say so clearly. Now, if you don’t accept this, and it turns out the bidder gets 90%, then a squeeze-out procedure (lunastusmenettely) follows. Your money will be tied up for a long time there. In the worst-case scenario, Nieminen has calculated/noticed that the 10% ownership threshold won’t be met, and he accepts the takeover bid at the last minute. And there wouldn’t be time for a flagging notification (liputusilmoitus) if the decision is made at the “eleventh hour.” Then some of the smaller investors would end up in the squeeze-out procedure “against their will”…

You can also gauge this by looking at the number of shareholders on Nordnet. The biggest drop has already occurred, and presumably, most current owners are holding out for a better price. There are now about 5,500 shareholders on Nordnet, and if each had, say, 200 shares, that would total around a million shares. These represent 5%, and together with Nieminen, we easily reach over 10% in total.

Everyone has to make that decision for themselves; personally, I have decided that my shares won’t go at that price except through the redemption procedure. I consider the offer value far too low compared to the company’s value, and I hope there are enough like-minded people so that they don’t get the required number of shares for the redemption procedure.

I think Nieminen is not selling. I doubt his spokesperson would have written this otherwise:   It is indeed a bit difficult to conduct a poll here on who is selling and who isn’t. Larger owners are unlikely to want to reveal the person behind their pseudonym because of this. I certainly don’t. And the number of votes and intentions shared through pseudonyms have an information value that is close to zero. If only there were some platform through which shareholders could verifiably declare their intentions and get a public and up-to-date summary without revealing names.

One would think that Nieminen isn’t selling, given that he has been buying so aggressively, likely with the intent of blocking the deal, so the rest of us should certainly support him in that. Nieminen should go public with his intentions.

I have to admit I’m quite lost at the moment as to whether to sell these Tecnotrees or what the smartest move with them would be…

If the goal has been to push the share price down and thereby make the premium look better, isn’t that quite logical behavior?

Tecnotree

Tecnotree announced yesterday that it had signed a continuation agreement with an existing Tier 1 telecom operator in the Middle East. The agreement supports revenue, but in our understanding, it is a continuation agreement, and thus it does not drive growth. 

Translation: Original published in Finnish on 6/27/2025 at 7:55 am EEST.
Tecnotree announced yesterday that it had signed a continuation agreement with an existing Tier 1 telecom operator in the Middle East. The agreement covers Tecnotree&apos;s digital BSS platform, and the annually renewable agreement (ARR) is valued at approximately 2 MUSD per year. Tecnotree expects to book revenues in Q3&#x2019;25. The agreement supports revenue, but in our understanding, it is a continuation agreement, and thus it does not drive growth. However, the company has recently announced large contracts, on which our comments can be read <a href="https://www.inderes.se/research/tecnotree-strong-sales-momentum-continues">here</a>.

Tecnotree announces follow-up agreement with Tier 1 customer

Login required

Forum discussions