BIZTRAC BETA
Computer programming activities

ONE CLICK PULSE AS

Org. no. 931719416 Limited company (AS) Fredrikstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 23,000
Incorporated 2023
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

ONE CLICK PULSE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 931719416. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Applikasjonsutvikling på mobil innenfor området små og enkle spørreundersøker.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 23,000
Est. value
NOK 42,000

Financial health · 2025

Liquidity
12.54
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
92.0%
Weak
Equity as a share of total capital

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

Who owns ONE CLICK PULSE AS?

GJERMUND BRÅTEN
ONE CLICK PULSE AS
NOK 0 rev. · NOK −7,000 profit

ONE CLICK PULSE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ONE CLICK PULSE AS

Who owns ONE CLICK PULSE AS?

GJERMUND BRÅTEN is the largest registered owner, with 60.0%.

What is the revenue of ONE CLICK PULSE AS?

ONE CLICK PULSE AS had revenue of NOK 0 in 2025.

Who is the general manager of ONE CLICK PULSE AS?

Gjermund Bråten is registered as general manager of ONE CLICK PULSE AS.

Where is ONE CLICK PULSE AS based?

ONE CLICK PULSE AS has its business address in Fredrikstad.

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.