BIZTRAC BETA
Business and other management consultancy activities

IGNIS TJENESTER AS

Org. no. 932933950 Limited company (AS) Horten Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 953,000
Operating profit NOK 797,000
Equity NOK 656,000
Incorporated 2024
Share capital NOK 30,000

IGNIS TJENESTER AS is registered as a limited company in Horten, Vestfold with organisation number 932933950. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen bedriftsrådgivning og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 953,000 in revenue and NOK 797,000 in operating profit.

Key figures · 2024

Revenue
NOK 953,000
Operating profit
NOK 797,000
Equity
NOK 656,000
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns IGNIS TJENESTER AS?

PER OLAV PETTERSEN
IGNIS TJENESTER AS
NOK 953,000 rev. · NOK 797,000 profit

IGNIS TJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IGNIS TJENESTER AS

Who owns IGNIS TJENESTER AS?

PER OLAV PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of IGNIS TJENESTER AS?

IGNIS TJENESTER AS had revenue of NOK 953,000 in 2024.

Who is the general manager of IGNIS TJENESTER AS?

Per Olav Pettersen is registered as general manager of IGNIS TJENESTER AS.

Where is IGNIS TJENESTER AS based?

IGNIS TJENESTER AS has its business address in Horten.

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.