SRE

Prezzo Sempra Energy

SRE
$93,87
-$1,92(-2,00%)

*Data last updated: 2026-04-17 19:54 (UTC+8)

As of 2026-04-17 19:54, Sempra Energy (SRE) is priced at $93,87, with a total market cap of $62,57B, a P/E ratio of 31,36, and a dividend yield of 2,70%. Today, the stock price fluctuated between $93,00 and $95,84. The current price is 0,93% above the day's low and 2,05% below the day's high, with a trading volume of 2,49M. Over the past 52 weeks, SRE has traded between $93,00 to $101,03, and the current price is -7,08% away from the 52-week high.

SRE Key Stats

Yesterday's Close$95,47
Market Cap$62,57B
Volume2,49M
P/E Ratio31,36
Dividend Yield (TTM)2,70%
Dividend Amount$0,65
Diluted EPS (TTM)2,81
Net Income (FY)$1,83B
Revenue (FY)$13,71B
Earnings Date2026-05-14
EPS Estimate1,48
Revenue Estimate$4,10B
Shares Outstanding655,47M
Beta (1Y)0.677
Ex-Dividend Date2026-03-19
Dividend Payment Date2026-04-15

About SRE

Sempra operates as an energy-services holding company in the United States and internationally. The company's San Diego Gas & Electric Company segment provides electric services; and supplies natural gas. It offers electric services to approximately 3.6 million population and natural gas services to approximately 3.3 million population that covers 4,100 square miles. Its Southern California Gas Company segment owns and operates a natural gas distribution, transmission, and storage system that supplies natural gas to a population of approximately 22 million covering an area of 24,000 square miles. The company's Sempra Texas Utilities segment engages in the regulated transmission and distribution of electricity serving 3.8 million homes and businesses, and operation of 140,000 miles of transmission and distribution lines. Its transmission system includes 18,249 circuit miles of transmission lines, a total of 1,174 transmission and distribution substations, and interconnection to 130 third-party generation facilities totaling 45,403 megawatts. The company was formerly known as Sempra Energy and changed its name to Sempra in July 2021. Sempra was founded in 1998 and is headquartered in San Diego, California.
SectorUtilities
IndustryDiversified Utilities
CEOJeffrey Walker Martin
HeadquartersSan Diego,CA,US
Official Websitehttps://www.sempra.com
Employees (FY)5,60K
Average Revenue (1Y)$2,44M
Net Income per Employee$328,03K

Sempra Energy (SRE) FAQ

What's the stock price of Sempra Energy (SRE) today?

x
Sempra Energy (SRE) is currently trading at $93,87, with a 24h change of -2,00%. The 52-week trading range is $93,00–$101,03.

What are the 52-week high and low prices for Sempra Energy (SRE)?

x

What is the price-to-earnings (P/E) ratio of Sempra Energy (SRE)? What does it indicate?

x

What is the market cap of Sempra Energy (SRE)?

x

What is the most recent quarterly earnings per share (EPS) for Sempra Energy (SRE)?

x

Should you buy or sell Sempra Energy (SRE) now?

x

What factors can affect the stock price of Sempra Energy (SRE)?

x

How to buy Sempra Energy (SRE) stock?

x

Risk Warning

The stock market involves a high level of risk and price volatility. The value of your investment may increase or decrease, and you may not recover the full amount invested. Past performance is not a reliable indicator of future results. Before making any investment decisions, you should carefully assess your investment experience, financial situation, investment objectives, and risk tolerance, and conduct your own research. Where appropriate, consult an independent financial adviser.

Disclaimer

The content on this page is provided for informational purposes only and does not constitute investment advice, financial advice, or trading recommendations. Gate shall not be held liable for any loss or damage resulting from such financial decisions. Further, take note that Gate may not be able to provide full service in certain markets and jurisdictions, including but not limited to the United States of America, Canada, Iran, and Cuba. For more information on Restricted Locations, please refer to the User Agreement.

Other Trading Markets

Hot Posts su Sempra Energy (SRE)

K-LinePoet

K-LinePoet

37 minuti fa
2026年3月13日, 桑普拉能源(SRE)披露1笔公司内部人交易情况。董事Kirk Jennifer M于2026年3月12日买入1000股。 **【近期内部交易】** | 披露日期 | 职位 | 姓名 | 交易日期 | 买/卖 | 数量 | 每股成交价/美元 | 总金额/美元 | | --- | --- | --- | --- | --- | --- | --- | --- | | 2026年3月13日 | 董事 | Kirk Jennifer M | 2026年3月12日 | 买入 | 1000 | 93.44 | 9.34万 | | 2026年3月11日 | 董事 | WARNER CYNTHIA J | 2026年3月11日 | 买入 | 2500 | 92.95 | 23.24万 | | 2026年3月11日 | 董事 | MARK RICHARD J | 2026年3月11日 | 买入 | 2692 | 93.30 | 25.12万 | | 2026年3月9日 | 高管 | Sedgwick Karen L | 2026年3月9日 | 卖出 | 2699 | 92.61 | 25.00万 | | 2026年3月9日 | 高管 | Sedgwick Karen L | 2026年3月9日 | 卖出 | 987 | 91.36 | 9.02万 | | 2026年3月9日 | 高管 | Sedgwick Karen L | 2026年3月9日 | 卖出 | 1186 | 93.52 | 11.09万 | | 2026年1月28日 | 董事 | Martin Jeffrey W | 2026年1月27日 | 卖出 | 1.73万 | 87.11 | 150.54万 | | 2026年1月28日 | 董事 | Sagara Kevin C. | 2026年1月27日 | 卖出 | 3605 | 87.11 | 31.41万 | | 2026年1月28日 | 高管 | DAY DIANA L | 2026年1月27日 | 卖出 | 508 | 87.11 | 4.43万 | | 2026年1月28日 | 高管 | Wold Dyan Z. | 2026年1月27日 | 卖出 | 254 | 87.11 | 2.22万 | **【公司资料】** Sempra成立于1998年,通过Enova和PE的业务合并,Enova和PE是公司在加利福尼亚州受监管的公用事业的控股公司:SDG&E于1881年开始运营,SoCalGas于1867年开始运营。公司是一家总部位于加利福尼亚州的能源服务控股公司。公司投资、开发和运营能源基础设施,并为北美客户提供电力和天然气服务。
0
0
0
0
Raveena

Raveena

8 ore fa
#AIInfraShiftstoApplications #AIInfraShiftstoApplications For decades, IT infrastructure was the star of the show. Physical servers, racks of blinking switches, storage arrays, and carefully patched network cables – these were the crown jewels of any enterprise. Teams measured success by uptime, capacity planning, and hardware refresh cycles. Applications were guests; infrastructure was the permanent, unshakeable host. That era is over. Quietly but decisively, infrastructure has lost its central role. Today, infrastructure exists for one reason only: to serve applications. More than that, infrastructure is no longer a separate layer to be managed in isolation. It is being absorbed, abstracted, and redefined by the very applications it supports. The statement “All infra shifts to applications” captures a profound change in how we build, run, and think about technology. What Does “Infrastructure Shifts to Applications” Actually Mean? Let’s break down the phrase. It does not mean that hardware disappears or that networks become irrelevant. Rather, it means: 1. Infrastructure is defined by application needs. Instead of asking “What servers do we have?”, we now ask “What does the application require in terms of latency, throughput, storage, and security?” Infrastructure adapts to the application, not the other way around. 2. Application code controls infrastructure. Through Infrastructure as Code (IaC) and policy‑as‑code, the same pipelines that build and test applications also provision, configure, and decommission infrastructure. The application’s deployment manifest is the infrastructure blueprint. 3. Observability shifts from boxes to services. Monitoring used to focus on CPU, memory, and disk. Today, we monitor transaction traces, error rates, and user experience. Infrastructure metrics are still there, but they are secondary signals that help explain application behaviour. 4. Teams reorganise around applications. The old separation between “dev” and “ops” is dissolving. Platform engineering, site reliability engineering (SRE), and developer experience (DevEx) teams exist to provide application‑facing abstractions. They treat infrastructure as an internal product whose users are other developers – not the hardware itself. The Historical Shift: From Pets to Cattle to Functions To understand this transition, look at the evolution of infrastructure thinking. · Pets era: Each server had a name and was lovingly hand‑configured. If it failed, it was a crisis. Applications were tied to specific machines. · Cattle era: Virtual machines and later containers made servers disposable. Infrastructure became programmable. But we still thought in terms of clusters, autoscaling groups, and load balancers. The application was one workload among many. · Functions and services era: With serverless compute (AWS Lambda, Cloud Functions) and managed services (databases, queues, object storage), infrastructure becomes an invisible utility. The developer writes code or configures an API; the platform handles placement, scaling, and fault tolerance. Infrastructure is no longer a distinct concern – it has shifted entirely into the application’s request cycle. This last stage is where “all infra shifts to applications” finds its full expression. The infrastructure is not hidden behind a layer of YAML files or Terraform scripts; it is abstracted to the point where most developers never touch a kernel, a virtual network, or a storage volume. Real‑World Manifestations You see this shift in every modern technology practice: #AIInfraShiftstoApplications · Serverless databases: Instead of provisioning a database server, an application connects to a connection string and pays per query or per second of compute. The infrastructure (backup, replication, failover) is completely managed by the provider and invisible to the app team. · Edge computing: An application deployed to a CDN worker (like Cloudflare Workers or Fastly Compute) runs code at the edge without the developer ever provisioning a server. The infrastructure is the application’s distribution logic. · API gateways and service meshes: These are infrastructure components, but they are configured through application‑aware policies – routing based on HTTP headers, retry budgets derived from service SLAs, canary deployments triggered by application metrics. · Platform engineering internal developer portals: Teams build “golden paths” where a developer declares an application name and desired capabilities (e.g., “PostgreSQL 14”, “public HTTPS endpoint”). The platform synthesises all required infrastructure – network, IAM, storage, compute – from that declarative application spec. Why This Matters for Your Career and Organisation For infrastructure engineers: Your role is no longer about racking and stacking. It is about building self‑service platforms, writing reusable modules, and teaching applications how to consume infrastructure safely. You become a product manager for internal infrastructure services. For developers: You can no longer say “it works on my machine” and throw problems over the wall. You own your application’s runtime behaviour, including how it interacts with infrastructure. Tools like OpenTelemetry, distributed tracing, and chaos engineering are now part of your daily toolkit. For business leaders: The old model of “buy hardware, depreciate over five years” is dead. Infrastructure spending moves to operational expense tied directly to application usage. More importantly, speed of application delivery becomes the primary competitive metric. Organisations that still require weeks to provision a database will lose to those that offer it in minutes via a self‑service API. Challenges on the Road Ahead Shifting all infrastructure to applications is not frictionless. Three major challenges emerge: 1. Abstraction leaks. No matter how high‑level the platform, sometimes you need to understand the underlying infrastructure. A cold‑start latency in a function, a noisy neighbour in a shared Kubernetes cluster, or a throttled storage API – these force developers to peek under the hood. Good platforms minimise leaks but cannot eliminate them entirely. 2. Cost control. When infrastructure is invisible and scales automatically with application load, costs can spiral. Each API call, each log line, each stored object becomes a micro‑transaction. Teams need new FinOps practices and cost‑awareness built into application design. 3. Security and compliance. Traditional network perimeters vanish. Security shifts to identity‑based policies (zero trust), workload attestation, and application‑layer controls. Auditors accustomed to firewall rules and VLANs must learn to read infrastructure‑as‑code policies and service mesh authorisation logs. Conclusion: Embrace the Shift “All infra shifts to applications” is not a slogan – it is a description of where technology has already arrived. The most innovative companies no longer manage infrastructure directly. They write applications, and the infrastructure materialises around those applications, on demand, ephemeral, and precisely sized. #AIInfraShiftstoApplications Your path forward is to adopt this mindset. Stop asking “What infrastructure do we have?” Start asking “What does my application need?” Automate the provisioning. Abstract the complexity. Measure everything from the application’s perspective. When you do, you will find that infrastructure is no longer a separate burden – it is just another feature of your application, delivered automatically. The shift is complete. The infrastructure has become the application’s shadow – always present, never in the way. Welcome to the new normal.#AIInfraShiftstoApplications
1
1
0
0