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


qlife-holding-ab-update-on-the-reverse-takeover-process-red-chip-structure-will-not-be-approved-by-nasdaq-other-structures-are-pursued-1

__typename

title

isPremium

lang

htmlBody

summary

companies

createdAt

publishers

authors

reactionGroups

pageUrl

translations

imgUrl

description

Qlife Holding AB is a med-tech group that strives to revolutionize the market for clinical biomarkers and virus tests. By enabling tests at home as a complement to tests in healthcare, access to important health information is facilitated, which can contribute to better treatment and potentially prevent diseases. The first capsules in the company's product, Egoo.Health Platform, were CE-marked for professional use in early 2020. The company has patent protection for key parts of its technology. The Danish-based company is listed on Nasdaq First North Stockholm.

Qlife Holding

Qlife Holding AB ("Qlife" or "the Company") and Hipro Biotechnology Co., Ltd. ("Hipro") are working on the planned reverse takeover, as announced in press releases on 5 June 2025 and 5 October...

<div class="abstract">Qlife Holding AB ("Qlife" or "the Company") and Hipro Biotechnology Co., Ltd. ("Hipro") are working on the planned reverse takeover, as announced in press releases on 5&nbsp;June&nbsp;2025 and 5&nbsp;October 2025. Hipro is currently working on obtaining the required shareholder approvals to be able to carry out the reverse takeover. The companies' legal advisors in China have recommended a transaction structure for the reverse takeover called a "Red Chip" structure, which means that Qlife is to acquire Hipro through overseas entities.Nasdaq Stockholm AB ("Nasdaq") has now informed that the Company will not be approved for continued listing if the Company carries out the "Red Chip" structure. The reason for this is that such structure does not meet Nasdaq's requirements for listing at Nasdaq First North and that in order for Nasdaq to approve it, they would likely need to consider certain changes to their rules and processes. </div>Qlife remains fully committed to completing the transaction and is currently pursuing alternative structures with Hipro and its advisors in order to complete the transaction as announced. Qlife and Hipro continue to work closely together in their operations and are strongly convinced that the intended transaction will create significant shareholder value, driven by the operational and strategic synergies between the companies. Qlife is dedicated to maintaining transparency and working constructively with Nasdaq to identify a compliant and sustainable solution. Further information about the intended terms of the transaction can be found in the press releases published on 5 June and 5 October 2025: "Qlife Holding AB: Qlife enters letter of intent with Hipro Biotechnology Co., Ltd. to join forces through a reverse takeover" and "Qlife Holding AB: The Letter of Intent with Hipro Biotechnology Co., Ltd. regarding reverse takeover has been extended".Further updates will be communicated as the process advances.<div></div>

Qlife Holding AB: Update on the reverse takeover process - "Red Chip" structure will not be approved by Nasdaq - other structures are pursued