based on your screenshot you seem to have a proprietary encapsulation in the UDP payload (we can see the string nr-rrc and a BCCH-BCH message - that contains a MIB - is 3 bytes long only). So presumably here the real data you want to decode is 0x06f2d4?
You should request to whoever defined this encapsulation the corresponding Wiresahrk dissector / plugin that calls the NR-RRC dissector. Or use another encapsulation method as the one described by Anders.
For the payload 06f2d4, the decoding is:
NR Radio Resource Control (RRC) protocol BCCH-BCH-Message message: mib (0) mib systemFrameNumber: 0c [bit length 6, 2 LSB pad bits, 0000 11.. decimal value 3] subCarrierSpacingCommon: scs15or60 (0) ssb-SubcarrierOffset: 15 dmrs-TypeA-Position: pos2 (0) pdcch-ConfigSIB1 controlResourceSetZero: 5 searchSpaceZero: 10 cellBarred: notBarred (1) intraFreqReselection: allowed (0) spare: 00 [bit length 1, 7 LSB pad bits, 0... .... decimal value 0]