BIZTRAC BETA
Business and other management consultancy activities

BFS RÅDGIVNING AS

Org. no. 923306064 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 717,000
Equity NOK 1.0m
Incorporated 2019
Share capital NOK 30,000

BFS RÅDGIVNING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 923306064. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulenttjenester og produkter knyttet til forretningsdrift av selskaper i videste forstand, samt andre produkter og tjenester som naturlig faller sammen med dette. Herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 717,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 717,000
Equity
NOK 1.0m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns BFS RÅDGIVNING AS?

FRODE STØRDAL
BFS RÅDGIVNING AS
NOK 2.6m rev. · NOK 717,000 profit

BFS RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BFS RÅDGIVNING AS

Who owns BFS RÅDGIVNING AS?

FRODE STØRDAL is the largest registered owner, with 100.0%.

What is the revenue of BFS RÅDGIVNING AS?

BFS RÅDGIVNING AS had revenue of NOK 2.6m in 2024.

Where is BFS RÅDGIVNING AS based?

BFS RÅDGIVNING AS has its business address in Trondheim.

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.