BIZTRAC BETA
Business and other management consultancy activities

LEADIFY AS

Org. no. 917677204 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 10.2m
Operating profit NOK −468,000
Equity NOK 2.1m
Incorporated 2016
Employees 6
Share capital NOK 75,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−468k kr).

LEADIFY AS is registered as a limited company in Stavanger, Rogaland with organisation number 917677204. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016 and has 6 registered employees. Registered share capital is NOK 75,000, divided into 75 shares. The company's stated purpose is: “Tjenester innen digital markedsføring og salg, samt andre tjenester, programvare og produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.2m in revenue and NOK −468,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.2m
Operating profit
NOK −468,000
Equity
NOK 2.1m
Est. value
NOK 11.7m

Financial health · 2024

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.8%
Good
Equity as a share of total capital

Who owns LEADIFY AS?

ØYVIND BØRGE JACOBSEN
LEADIFY AS
NOK 10.2m rev. · NOK −468,000 profit

LEADIFY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEADIFY AS

Who owns LEADIFY AS?

ØYVIND BØRGE JACOBSEN is the largest registered owner, with 100.0%.

What is the revenue of LEADIFY AS?

LEADIFY AS had revenue of NOK 10.2m in 2024.

Who is the general manager of LEADIFY AS?

Øyvind Børge Jacobsen is registered as general manager of LEADIFY AS.

Where is LEADIFY AS based?

LEADIFY AS has its business address in Stavanger.

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.