BIZTRAC BETA
Other education activities

REGLOWING AS

Org. no. 931954083 Limited company (AS) Årdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 79,000
Operating profit NOK −213,000
Equity NOK −73,000
Incorporated 2023
Share capital NOK 174,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−73k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−213k kr).
  • Nylig endring 2026-06-25 Konkurs registrert 2026-06-25.

REGLOWING AS is registered as a limited company in Årdal, Vestland with organisation number 931954083. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2023. Registered share capital is NOK 174,000, divided into 174 shares. The company's stated purpose is: “Digitale tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 79,000 in revenue and NOK −213,000 in operating profit.

Key figures · 2024

Revenue
NOK 79,000
Operating profit
NOK −213,000
Equity
NOK −73,000

Financial health · 2024

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-49.6%
Weak
Equity as a share of total capital

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

Who owns REGLOWING AS?

Angelica Kivikoski
REGLOWING AS
NOK 79,000 rev. · NOK −213,000 profit

REGLOWING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REGLOWING AS

Who owns REGLOWING AS?

Angelica Kivikoski is the largest registered owner, with 50.0%.

What is the revenue of REGLOWING AS?

REGLOWING AS had revenue of NOK 79,000 in 2024.

Who is the general manager of REGLOWING AS?

Angelica Kivikoski is registered as general manager of REGLOWING AS.

Where is REGLOWING AS based?

REGLOWING AS has its business address in Øvre Årdal.

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

Report a problem

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