biztrac. BETA
COMPANY REGISTER PROFILE
929723279 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠REGALIA AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Retail sale of cultural and recreational goods n.e.c.

REGALIA AS

Org. no. 929723279 Limited company (AS) Nes Incorporated 2022 In liquidation
Revenue 2025 NOK 18,000
Operating profit NOK −28,000
Equity NOK 2,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

REGALIA AS is registered as a limited company in Nes, Akershus with organisation number 929723279. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av profileringsartikler og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 18,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 18,000
▼ −37 %
Operating profit
NOK −28,000
▼ −203 %
Equity
NOK 2,000
▼ −93 %

Financial health · 2024

Liquidity
3.15
Very good
Current assets ÷ current liabilities
Profitability
-20.1%
Not satisfactory
Return on total assets
Solidity
69.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns REGALIA AS?

REGALIA AS
NOK 18,000 rev. · NOK −28,000 profit

REGALIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REGALIA AS

Who owns REGALIA AS?

SIGN GROUP NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of REGALIA AS?

REGALIA AS had revenue of NOK 18,000 in 2025.

Where is REGALIA AS based?

REGALIA AS has its business address in Årnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.