Kimmono (@kimmono) profile picture

Support @Arsenal, interests: UAP, AI, Ukraine and Energy.

Oslo, Norway
Joined February 2008
Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)Photo by Kimmono (@kimmono)
💔✨ FAREWELL TO A BRAVE SCIENTIFIC PIONEER — RUSSELL TARG, A MAN WHO DARED TO EXPLORE THE ‘IMPOSSIBLE’ ✨🕊️ Friends… I am deeply saddened by the passing of Russell Targ - a remarkable scientist, a pioneer, a visionary, and a man for whom I had ENORMOUS respect and admiration. Some of you may not recognise his name. But I believe he will be remembered as one of the BRAVEST scientific explorers of the modern age. Let me explain WHY. Russell was a brilliant physicist who helped pioneer the development of LASERS & optical communications. His scientific achievements even earnt him TWO NASA awards. He could have spent his career working safely within the accepted boundaries of conventional science, but he had the COURAGE TO ASK QUESTIONS THAT OTHERS WERE AFRAID TO ASK! In the early 70s, Russell and Hal Puthoff worked with me & other psychics, such as Pat Price & Ingo Swann, to investigate TELEPATHY, CLAIRVOYANCE and REMOTE VIEWING - risking their reputations! In one of the experiments, they placed me inside a specially shielded room & asked me to psychically perceive & reproduce a series of (randomly chosen) hidden drawings & other targets. The results of these tests were irrefutably successful! So much so, that in1974, they published a groundbreaking scientific paper, 'Information Transmission under Conditions of Sensory Shielding', in one of the world's most prestigious scientific journals - NATURE. As well as this pioneering work, Russell also helped develop REMOTE VIEWING & the CIA's STARGATE programme, which officially continued for 20 years (but I KNOW is still ongoing). He went on to write many fascinating books, including Mind Reach and Limitless Mind, exploring consciousness and the human potential and he gave illuminating talks and appeared in documentaries like 2019’s Third Eye Spies (in which I also appeared with him). And he never stopped asking questions. That is why I believe his legacy will continue LONG after the arguments surrounding his research – and that of other scientists who have “dared” to step outside of the confines of the currently “acceptable” and prevailing paradigms - have long faded away and been resolved. TODAY, many scientists are still reluctant to investigate unusual phenomena - not because they have examined the evidence & rejected it, but because they fear what their colleagues might say. They fear losing credibility, funding, promotions or professional standing - & their curiosity is silenced by fear! So, THANK YOU Russell, for your curiosity, for your integrity & your willingness to investigate. And above all, for your COURAGE! REST IN PEACE Or perhaps I should say… KEEP EXPLORING, MY FRIEND. ❤️✨ #RussellTarg #RemoteViewing #StargateProject #Consciousness #ESP #Science #InMemoriam
29
73
24
503
16,914
"...but also that the same officer "subsequently contacted IOD [Intelligence Oversight Directorate] and informed IOD that the information in question had been properly coordinated so there was no unauthorized disclosure" So the Grusch disclosure was coordinated?
GRUSCH LOSES FOIA LAWSUIT AGAINST DEFENSE DEPARTMENT Former intelligence officer David Grusch today (November 20, 2026) lost his federal lawsuit against the Department of Defense (DoD), challenging the DoD's handling of his October 2024 FOIA request, pertaining to an apparently short-lived security inquiry about Grusch in 2023. After months of written briefs and a live hearing today with lawyers from both sides, Federal District Judge Leonie M. Brinkema issued summary judgment in favor of the government. (See attached "Civil Motion Minutes.") Judge Brinkema will issue a written order later, which might include some analysis of why she rejected Grusch's claims that the DoD conducted an inadequate search for responsive records. In his lawsuit, Grusch claimed that the DoD conducted an inadequate search in response to his October 2024 FOIA request for certain documents related to a purported "unauthorized disclosure complaint" about Grusch, or related to any "unauthorized disclosure complaint" involving UAP/UFO, both limited to April 1 through December 31, 2023. In May 2026, the Department turned over 40 pages of partly redacted documents to Grusch, but Grusch did not make those documents public at the time. On June 25, I obtained a version of the same packet through my own FOIA request and published it. That release included a copy of a letter (attached below), dated November 1, 2023, to Congressman Tim Burchett (R-TN), from Mark D. Dupont, Principal Deputy and Senior Intelligence Oversight Official in the Office of the Assistant to the Secretary of Defense for Privacy, Civil Liberties, and Transparency. The Dupont letter was sent in response to an inquiry on Grusch's behalf from Burchett's office. In the letter, Dupont related that an unnamed Air Force Intelligence Oversight (IO) officer had reported that "the Air Force had received preliminary information that raised concerns about a possible unauthorized disclosure of classified information" by Grusch, but also that the same officer "subsequently contacted IOD [Intelligence Oversight Directorate] and informed IOD that the information in question had been properly coordinated so there was no unauthorized disclosure, and no follow-on action was necessary. At no point did anyone from the Air Force file a complaint with IOD and IOD took no actions with respect to these conversations." In my view, Dupont's letter described an incident markedly less dramatic than Grusch's later characterization, in a May 5, 2026 interview, that "the Air Force, I think, was very afraid when I went public.... it's come to my attention that when I went public in June 2023, the Department of the Air Force filed an unauthorized disclosure Espionage Act complaint against me." [See attached video clip.] Although Rep. Burchett, and presumably Grusch, received the Dupont letter in November 2023, it was never made public until I published it on June 25, 2026. To my mind, this entire episode is an example of something I wrote in a long article published on October 30, 2026, as follows: Some of the UAP whistleblowers have spoken in testimony and on podcasts regarding their actions in submitting claims to inspectors general, law enforcement agencies, AARO, and courts, but few have been forthcoming in sharing documents on the end products of the ensuing inquiries. Regarding the outcomes of independent inquiries, what has come into the public domain mostly has not been through voluntary disclosures by the attestants or the "disclosure" organizations, nor through reports flowing from any congressional investigations properly so called, but piecemeal through independent, time-consuming Freedom of Information Act (FOIA) requests and other forms of investigatory journalism. Notably, when authoritative documents have come to light through FOIA or other means, they have on multiple occasions conflicted with the widely disseminated narratives of certain prominent storytellers. Perhaps this is one reason why most of the current array of publicly identified UAP "whistleblowers" assiduously avoid any public venue in which they would be subjected to sustained lines of questioning from well-informed persons who are not already cheerleaders. Grusch has still not released what he wrote on the form that he filled out for Rep. Burchett's office on October 4, 2023, in response to the question, "Briefly explain how the Congressman can be of assistance to you. Please attach additional copies of any relevant information:" Grusch's written explanation to Burchett was redacted on privacy grounds in the copy that I received via my FOIA request (see attachment; there was another following page that was also fully redacted in the copy that I received). Thus, we are not going to see Grusch's 2023 explanation to Burchett, unless Grusch chooses to release it. Most of the key documents in the Grusch FOIA lawsuit (Grusch v. Department of Defense, U.S. District Court for the Eastern District of Virginia, Alexandria Division, No. 1:26-cv-607) are available for free from CourtListener at courtlistener.com/docket/723…
1
51
Kimmono retweeted
NEW: Today‘s PURSUE release includes the first analysis of radar tracks, which suggest that a UAP flew at approximately 1,650 mph (~Mach 2.5) and 55,000 - 70,000 feet while changing directions. war.gov/medialink/ufo/docs-1…
13
68
7
289
8,971
The @EU_Commission should also investigate the 10x price increase on DDR5 memory! This is a disaster for innovation and privacy in Europe, as it is too expensive to buy hardware for Local AI, PC and servers. @vonderleyen
A federal court in California found that the plaintiffs’ allegations plausibly suggest Samsung, SK hynix, and Micron agreed to restrict DRAM supply. The court denied the three companies’ motion to dismiss, allowing the antitrust lawsuit to proceed.
1
74
Six of Nvidia’s seven biggest customers are building their own chips. “NVIDIA’s seven biggest customers account for the vast majority of GPUs being deployed: Google, Microsoft, Meta, Amazon, SpaceX, Anthropic and OpenAI. All of them, except SpaceX, are making their own chips.” “If NVIDIA didn’t prop up CoreWeave and the other neoclouds, those industries just would not exist, and the hyperscalers would have full control.” “Jensen’s the only executive in the semiconductor industry convincing supply chain companies to invest like they’ve never done before. From our benchmarking, the TPU is just as good as NVIDIA. But Google doesn’t have that DNA of wheeling and dealing.”
138
247
65
2,428
343,219
Anthropic reported a similar sudden and unusual jump in robotics capabilities with Fable 5.2. As the general intelligence of frontier models scales up, it is increasingly surpassing specialized training. This will ultimately generalize to every sphere of human ability.
Fortune is reporting that OpenAI is so convinced that LLMs will become brains for robots that it has disbanded its robotics team.
87
189
40
2,187
131,624
Yesterday, before digging into The Flight Situation, I wrote: "If the RADARs were being jammed, that should be detectable, that wouldn't be a mystery. Same with broad-spectrum comms jamming. So, if it's not from an exterior source, that points to widespread system degradation; and I can't *imagine* a way that happens accidentally (unless an implementation is mind-bendingly stupid, in a way I genuinely struggle to fathom)." Hoo, boy. I was hoping for more info today but, IMO, the important info isn't from today at all. We have a full on Story Time on our hands. But, first, the immediate updates: Good news is that the FAA's comms are is back online, flights are moving again. The bad news is that "mind-bendingly stupid" was... kind of an understatement. I was not pessimistic enough, and that's truly saying something. Would it be embarrassing if this was the result of ignoring 20 weeks of warnings? This one's gonna get a *little* less objective as we go. Starting with the objective stuff: 1. What's up with flights? The nationwide ground stop ended Friday at 8:15 PM Eastern, after four hours and some change. Unfortunately, that doesn't mean the airlines are back to normal. More than 9000 commercial flights (and 3000 private ones) were canceled yesterday, and another 4–5000 are being canceled today, with who-knows-how-many-thousands more delayed. The problem now is mostly logistical. Aircraft and crews are scattered across the country, passengers have missed connections, and airlines have to rebuild their schedules in light of the, uh, shitshow. They can't just resume every canceled flight: the plane and crew that were supposed to run it may just be on the other side of the country (they were stranded, yesterday, too). And, unlike most industries, "just fly overtime" isn't on the table. Pilots and flight attendants operate under strict FAA duty-time and mandatory rest rules. Once a crew "times out" waiting through a four-hour ground stop, they're legally grounded until they get mandatory rest — and with airlines already running on tight pilot staffing (guess those chickens are coming home to roost), there just isn't a deep bench of spare crews to swap in. But, all that said, the FAA expects schedules to return to normal by the end of Sunday (so, I expect Tuesday), although some unlucky winners are probably going to see this run longer. Sorry. If you're planning on flying this weekend, check your flight status directly with the airline before heading to the airport (I would like to say "surely I don't need to write this", but). 2. So, what broke? We now have a (hilarious, watch the video) preliminary explanation from Transportation Secretary Sean Duffy and the FAA. Yesterday, a contractor called L3Harris was performing routine maintenance at a remote FAA facility, migrating telecommunications connections from 1980s-era copper lines to fiber. This did not go as planned. A new router started flooding the FAA's private network with "over 1000 connection attempts every few seconds" (either because of installer error or faulty hardware, they're still figuring it out -- but, looks like not a cyberattack! 🎊). Now, if you know networking, 1000 connection requests every few seconds isn't a lot. In 2026. A cheap cloud server shrugs that off. Your phone can do that. But, because it was interfacing with hardware from the dinosaur era — aging routers and switches built for tiny, predictable aviation circuits — *now* "1000" is a lot. The modern hardware overwhelmed the ancient hardware, causing widespread instability in the communications and radar data reaching air traffic controllers. Importantly, this does NOT mean all the physical radar installations stopped working. The sensors were still collecting information; the network just wasn't delivering that information to the people that needed it. That's consistent with what we found yesterday: the external radar, GPS, and weather data I checked looked normal, even as the national air traffic system was shutting down. The new equipment reportedly remained operational; the old infra just couldn't deal. Once engineers isolated the affected work, the network stabilized. Sick. 3. What don't we know? The FAA hasn't completed its root-cause investigation (the FAA is thorough: this will probably take time). Officials are still examining whether this was contractor error, faulty equipment, or some combination of the two. "No cyberattack" is holding up, god bless. But, I think there's a much more important question than which router malfunctioned: How in, pardon, the *actual* fuck did maintenance at one (1) remote facility cause a nationwide (🇺🇸) failure? I used to be an analyst; I'm currently a software dev. We *have* SOPs for isolation, unit tests, failovers, and rollbacks *because* we know things go wrong. This is like Engineering 101. Shit happens, bring a raincoat. Equipment fails. People get hungry or sleepy or pissy and make mistakes. Sometimes, there's just some genuinely unexplainable bullshit: god has a sense of humor, and he's laughing at developers. That's the entire reason critical infra is supposed to have fault isolation, redundancy, tested fallback paths, and rollback procedures. We don't yet know whether those safeguards were absent yesterday, if they failed, or if someone just didn't use them correctly. We *do* know that whatever safeguards were in place, if any, didn't *work*. Sometimes, it's some genuinely unexplainable bullshit: a real "who could've seen this coming?" This was *not* one of those times, lmao. 4. How did we get here? On October 31, 2005, the FAA suffered an outage during a telecommunications migration at Chicago O'Hare: some comms gear failed, controllers lost radar picture (equipment still working, they just couldn't see it: sound familiar?), and air traffic had to be restricted. The Department of Transportation's Inspector General investigated and published its findings in April 2006 (Report AV-2006-047). Among the failures it identified: inadequate coordination with local engineers, incorrect equipment requirements, and a... "problem with the backup system" isn't quite right. That sort of implies the backup system exists. When the FAA tried to switch to its backup, it discovered that the backup service wasn't available because: nobody had tested and verified that the backup line actually existed. So, setting aside objectivity for a second: Are you fucking kidding me? lmao? The IG (inspector general) recommended "improving transition planning, verifying site requirements, and ensuring that migrations didn't disrupt air traffic operations". Would it be embarrassing if the warnings were ignored for 20 weeks? How about 20 *years*? 5. Oh it gets worse. 2023: an independent FAA safety review warned that the national telecommunications backbone was "dangerously obsolete". The report explicitly identified budget constraints as a reason the FAA remained dependent on ancient technology. It said the FAA had *already* classified the infrastructure risk at its highest level. We're not done: in September OF THIS YEAR, the Government Accountability Office (GAO) published another warning (GAO-26-107992) about the accelerated $12.5 billion modernization program: among other things, they found that the FAA lacked a reliable overall cost estimate, and had 11,000+ individual project schedules that hadn't been integrated into a master schedule. GAO specifically warned that this made it harder to "coordinate installations" and "minimize disruption to air traffic operations". So: who could've seen this coming? Hellen fucking Keller could've seen this coming. None of this establishes *which* management issues contributed to yesterday's... situation... but, the fact that there are "too many issues to narrow it down to one" is actually a joke. 6. Now what? I think two things can be true simultaneously: A: The FAA desperately needs to replace this aging infrastructure. Decades of funding problems, procurement difficulties, and delayed modernization have created a genuinely dangerous situation. B: Replacing that infrastructure without adequate safeguards (read: yesterday) can *also* be a problem. Damned if you do, damned if you don't. The FAA, and aviation culture in general, are usually commendably safety-conscious (borderline neurotic, in a good way) — just like with crew rest rules, they don't fuck around. Their safety mechanism here was basically "this is sketchy, ground everything": working as intended, even if it never should have been required. Apparently, the same simply cannot be said of the infrastructure surrounding aviation. At this point, the FAA's investigation needs to establish exactly how this failure propagated, what redundancy existed (if any), whether fallback and rollback procedures were tested, and, ultimately, explain how a local maintenance operation could compromise operations nationwide. Yesterday, I said I couldn't imagine a widespread accidental failure unless the implementation was "mind-bendingly stupid". My mind is now bent. And, to be clear, the issue isn't "a technician made one stupid mistake". Shit happens. The part that really makes you wonder is how, despite twenty years of documented warnings, the system *still* didn't have a raincoat.
Sorry for the long-ass post, I did some OSINT shit. I pulled live public flight feeds, weather radar status, and space weather data to see what's actually going on during today's nationwide FAA grounding. TL;DR: radar, GPS, and weather sensors are all working fine. What broke is the long-distance communications network that lets the FAA's 22 regional air traffic control centers talk to high-altitude planes and hand them off to each other. When people think of air traffic control, they picture the glass tower at an airport. Those towers only handle takeoffs, landings, and nearby airspace. Once a plane climbs out, it's handed off to one of 22 regional Air Route Traffic Control Centers (ARTCCs) — giant facilities that manage high-altitude cruising traffic across whole regions of the country. Normally, those 22 centers are regionally isolated: if one loses power or a local fiber line, neighboring centers absorb or route traffic around it. Having all 22 degrade at once is virtually unheard of because it means a shared national backbone failed, leaving no healthy neighbor to take over. That's why the FAA's Command Center used such stark, blanket wording ("Due to extraordinary circumstances and for reasons of safety... all airports are ground stopped until further notice"*) — it's standard protocol when a national-level freeze has to happen immediately before engineers even know how long repairs will take ("safety issue" means "oh shit, stop" in aviation circles, unlike with AI companies). All 22 centers losing comms at once is, indeed, "extraordinary circumstances". Here's what the live data shows: 1. US airspace is emptying out fast. Normally on a Friday evening, thousands of planes are in the air over the US. In live tracking data from OpenSky Network, the number of airborne planes over the lower 48 is steadily draining as flights land and no new commercial departures take off: • 6:36 PM EST: 1,083 airborne • 6:42 PM EST: 1,035 airborne • 6:49 PM EST: 990 airborne There are zero emergency distress codes broadcasting. 2. Major airports are, predictably, stacked. Looking within 30 miles of major hubs around 6:37 PM EST (`adsb.lol`), almost nothing is moving: • NYC/JFK area: 8 in the air vs. 67 on the ground • LAX: 14 in the air vs. 40 on the ground • Dallas (DFW): 7 vs. 36 • Denver (DEN): 13 vs. 29 • Atlanta (ATL): 5 vs. 25 • Chicago (ORD): 9 vs. 24 • DC (DCA): 8 vs. 22 A lot of the coastal airports had to stop accepting diverts. 3. The few planes still taking off are enlightening. Across the entire US at 6:36 PM, only aircraft were taking off (that is: below 10,000 feet and climbing). They fell into two clear buckets: • 3 international widebody jets (`DAL281` out of Seattle, `DAL156` out of NYC, and `AFR71E` out of Newark), matching the FAA's note that international flights are being handled case-by-case. • Small private planes and a couple of business jets flying under VFR (visual flight rules) — essentially, staying below 18,000 feet, where pilots don't need en-route air traffic control clearances. Honorable mention to the 1 Coast Guard/military helicopter climbing near Tampa, out of 29 military aircraft tracked nationwide. 4. Weather radar isn't down, and there's no solar storm or GPS jamming. A lot of people wondered if today's FAA ground stop, rumors of a National Weather Service outage, and Microsoft's 365 outage were all connected. Checking the raw feeds: • Weather radar: 199 out of 208 US Doppler radar stations are actively sending fresh scans (within the last 15 minutes). The "NWS outage" rumors were website and caching glitches, not offline radar hardware. • GPS & Space Weather: NOAA space weather is completely quiet (`Kp = 0`), and aircraft GPS accuracy readings across the Midwest and Northeast look totally normal. • Local airport radar & towers: Local FAA ground-station radar broadcasts and local airport control towers are still up and transmitting. So, local sensors and local towers are fine. The failure is specifically in the long-haul telecommunications backbone connecting the FAA's 22 en-route centers to their remote radio sites — which is why en-route controller frequencies went quiet while local towers, weather radars, and low-altitude visual flights kept running. Federal officials say there's no sign of a cyberattack, so we're waiting on the FAA's technical post-mortem for what tripped the national network. That doesn't rule out a cyberattack as the root cause of the comms outage; it's a "we don't know". Shoutout to adsb.lol for their free API.
4
22
5
74
8,969
GROUNDSTOP. Let's talk about the FAA funding question. Sec. Duffy says he wants $50 billion and has pointed to a lack of Congressional funding as the issue. Here is the reality... thread.
20
144
11
566
83,949
Kimmono retweeted
After Democrats flipped both chambers of Congress in the midterm elections, the House Oversight Committee is considering a further investigation into the UAP files.
15
32
13
130
39,782
This is clearly not drones, this i UAP(s).
Footage of suspected drones near RAF Marham. Which is not far from Lakenheath/Mildenhall/Feltwell
103
News: The US intel community is still working to understand the relationship between a Chinese businesswoman who had an affair with Nvidia CEO Jensen Huang and the Chinese government, with multiple sources telling CNN that the intelligence collected on her to date does not prove that she was acting as a spy for Beijing. cnn.com/2026/11/12/politics/…
405
955
389
5,299
2,630,202
Kimmono retweeted
Nvidia chips are still scarce, even now. But to maximize that premium, Nvidia has to support the neoclouds. If the new Nvidia CEO turns even slightly skeptical about supporting the neoclouds, spot prices will take a hit. That will hurt neocloud margins. To avoid this, the neoclouds will have no choice but to reach out elsewhere. AMD, or the TPU camp. In other words, the neoclouds break free of Nvidia's grip, and Nvidia's dominance and influence both take a hit. That in turn means a hit to the massive order volume that underpins Nvidia's only moat, its control of the supply chain, and it means Nvidia's flywheel breaks. Jensen worked tirelessly to protect this flywheel. He pushed on many fronts to get a blind eye turned to neoclouds leasing capacity to Chinese hyperscalers, and he encouraged chip exports to China so that China would never forget the taste of the Nvidia sauce, working relentlessly to have China's AI ecosystem built on top of Nvidia. That way, even if the latest GPUs become hard to get inside China, there is still a reason to rent the same chips from overseas neoclouds. Keeping Chinese developers inside the Nvidia ecosystem was also a way of protecting neocloud utilization. Still, all of this was playing with fire along the edges of the gray zone, something deeply improper and dangerous in the eyes of Washington. Even so, Jensen did what was best for Nvidia. That cannot be denied. Jensen meant to wait until the neoclouds could order the next generation of GPUs on their own. He probably saw sharing risk with customers until then as being in Nvidia's interest too. What I want to know now is whether the next CEO can wait that long. According to the WSJ article... the current CEO does not seem to be that patient. I worry about an Nvidia without Jensen.
83
176
29
1,605
275,219
25 million Trump voters stayed home in the midterms, and 3.6 million switched sides.
29
379
32
900
25,868
As I predicted, Claude is off the leash. Fable 5.2 has solved two open problems in theoretical physics, one of them completely autonomously.
When you look at a frozen river, you must also imagine the current raging beneath the ice. I think all three big labs have achieved autonomous research and their internal models can now choose their own research directions. We will begin to see the fruits of this work this month.
76
234
27
2,145
88,375
Benchmarks:
Introducing Claude Fable 5.2 and Claude Mythos 5.2, designed to tackle the most daunting technical challenges. They’re capable collaborators on ambitious projects in many fields, and show improvements in areas like coding, reasoning, and vision.
17
24
4
424
33,767
Kimmono retweeted
President Trump says Air Force pilots told him in the Oval Office that a mysterious round object flew past an F-22 fighter jet at three times its speed, describing an encounter that defies conventional aerodynamics. Trump called the pilots "the real deal" and said they had shared "things that are very strange." He described himself as "not too much of a believer" but said the accounts from these aviators stood out. The object, he said, was round, not aerodynamic, and moved far faster than what he called "the best plane that anyone's ever seen." When asked whether a secret government program studying UFOs could exist without a president's knowledge, Trump said he hadn't heard of one, but pledged to find out. Full story here foxnews.com/us/trump-air-for…
81
278
22
1,602
209,242
Kimmono retweeted
China’s Space Program: Major Future Missions Revealed. 🧐 @NASAAdmin Source: teapaw.org/AJ_FI/status/211975945…
🤖 Made with AI
Slide on Chinese space timelines: Dec. 2027: Asteroid redirect mission 2028: Tianwen-3 Mars sample return, return 2031 2030: Tianwen-4 Jupiter mission By 2049: reach 80-100 AU, build a full-domain deep space exploration system. 2026-2034: large scale megaconstellation deployment
6
42
3,608
Across our projects @GoogleDeepMind, we are witnessing a genuine phase transition in the pace of scientific discovery. You will see a glimpse of this in our releases in the next few weeks.
299
785
286
9,369
1,192,029