biztrac. BETA
COMPANY REGISTER PROFILE
926278541 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠SWIPEINVITE AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Computer programming activities

SWIPEINVITE AS

Org. no. 926278541 Limited company (AS) Kristiansand Incorporated 2020 In liquidation
Revenue 2025 NOK 0
Operating profit NOK −120
Equity NOK −188,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−188k kr).

SWIPEINVITE AS is registered as a limited company in Kristiansand, Agder with organisation number 926278541. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av markedsføringstjenester og innsikt via egenproduserte digitale løsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −120 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −120
▲ +99 %
Equity
NOK −188,000
▼ −0 %

Financial health · 2025

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

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

Who owns SWIPEINVITE AS?

SWIPEINVITE AS
NOK 0 rev. · NOK −120 profit

SWIPEINVITE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SWIPEINVITE AS

Who owns SWIPEINVITE AS?

Jon Kristoffersen Bøhn is the largest registered owner, with 100.0%.

What is the revenue of SWIPEINVITE AS?

SWIPEINVITE AS had revenue of NOK 0 in 2025.

Where is SWIPEINVITE AS based?

SWIPEINVITE AS has its business address in Nodeland.

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.