biztrac. BETA
COMPANY REGISTER PROFILE
997505549 ORG. NO. 2024 ACCOUNTS 9 SECTIONS
Bankrupt UPDATED 03.10.2026
⚠TIDYPAY AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Computer programming activities

TIDYPAY AS

Org. no. 997505549 Limited company (AS) Nordre Follo Incorporated 2011 Bankrupt
Revenue 2024 NOK 5.6m
Operating profit NOK −25.8m
Equity NOK −16.0m
Incorporated 2011
Share capital NOK 8.9m

Signals

1 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.

TIDYPAY AS is registered as a limited company in Nordre Follo, Akershus with organisation number 997505549. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2011. Registered share capital is NOK 8.9m, divided into 5072067 shares. The company's stated purpose is: “Utvikling av software. Salg og import av varer og tjenester. Konsulentoppdrag innen finans, it og rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK −25.8m in operating profit.

Former names: FORTUNALIFE AS, LIVING CONSULTING AS, TIDYPOS AS

Key figures · 2024

Revenue
NOK 5.6m
▼ −3 %
Operating profit
NOK −25.8m
▲ +0 %
Equity
NOK −16.0m
▼ −102 %

Financial health · 2024

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
-200.4%
Not satisfactory
Return on total assets
Solidity
-142.9%
Weak
Equity as a share of total capital

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

Who owns TIDYPAY AS?

TIDYPAY AS has 18 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIDYPAY AS

Who owns TIDYPAY AS?

NEWDAY AS is the largest registered owner, with 94.6%.

What is the revenue of TIDYPAY AS?

TIDYPAY AS had revenue of NOK 5.6m in 2024.

Where is TIDYPAY AS based?

TIDYPAY AS has its business address in Trollåsen.

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.