BIZTRAC BETA
Business and other management consultancy activities

JN BEDRIFTSRÅDGIVNING AS

Org. no. 926454153 Limited company (AS) Fauske Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 15,000
Equity NOK 275,000
Incorporated 2021
Employees 5
Share capital NOK 30,000

JN BEDRIFTSRÅDGIVNING AS is registered as a limited company in Fauske, Nordland with organisation number 926454153. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bedriftsrådgivning innen forretnings- og eiendomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 15,000
Equity
NOK 275,000
Est. value
NOK 212,000

Financial health · 2025

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

Who owns JN BEDRIFTSRÅDGIVNING AS?

JAN NORMANN NILSEN
JN BEDRIFTSRÅDGIVNING AS
NOK 1.1m rev. · NOK 15,000 profit

JN BEDRIFTSRÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JN BEDRIFTSRÅDGIVNING AS

Who owns JN BEDRIFTSRÅDGIVNING AS?

JAN NORMANN NILSEN is the largest registered owner, with 100.0%.

What is the revenue of JN BEDRIFTSRÅDGIVNING AS?

JN BEDRIFTSRÅDGIVNING AS had revenue of NOK 1.1m in 2025.

Who is the general manager of JN BEDRIFTSRÅDGIVNING AS?

Jan Normann Nilsen is registered as general manager of JN BEDRIFTSRÅDGIVNING AS.

Where is JN BEDRIFTSRÅDGIVNING AS based?

JN BEDRIFTSRÅDGIVNING AS has its business address in Fauske.

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.