BIZTRAC BETA
Business and other management consultancy activities

NIM CONSULTING AS

Org. no. 934298810 Limited company (AS) Lier Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2
Equity NOK 94,000
Incorporated 2024
Share capital NOK 100,000

Signals

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

NIM CONSULTING AS is registered as a limited company in Lier, Buskerud with organisation number 934298810. 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 100,000, divided into 100000 shares. The company's stated purpose is: “Tilby høy faglig kompetanse og drive konsulent- og rådgivningsvirksomhet innenfor forsikring, økonomi og finans. I tillegg skal selskapet kunne gjøre andre strategiske investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2
Equity
NOK 94,000
Est. value
NOK 153,000

Financial health · 2024

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

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

Who owns NIM CONSULTING AS?

BIRGER PEDERSEN CONSULTING AS
NIM CONSULTING AS
NOK 0 rev. · NOK −2 profit

NIM CONSULTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NIM CONSULTING AS

Who owns NIM CONSULTING AS?

BIRGER PEDERSEN CONSULTING AS is the largest registered owner, with 70.0%.

What is the revenue of NIM CONSULTING AS?

NIM CONSULTING AS had revenue of NOK 0 in 2024.

Where is NIM CONSULTING AS based?

NIM CONSULTING AS has its business address in Lier.

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.