BIZTRAC BETA
Security and commodity contracts brokerage

LG & SP RÅDGIVNING AS

Org. no. 929343425 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 12.8m
Operating profit NOK 5.3m
Equity NOK 3.0m
Incorporated 2022
Share capital NOK 235,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LG & SP RÅDGIVNING AS is registered as a limited company in Oslo, Oslo with organisation number 929343425. The business is classified under security and commodity contracts brokerage (NACE 66.120). The company was incorporated in 2022. Registered share capital is NOK 235,000, divided into 196078 shares. The company's stated purpose is: “Investeringsrådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.8m in revenue and NOK 5.3m in operating profit.

Key figures · 2025

Revenue
NOK 12.8m
Operating profit
NOK 5.3m
Equity
NOK 3.0m
Est. value
NOK 13.7m

Financial health · 2025

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

Who owns LG & SP RÅDGIVNING AS?

FH KAPITAL HOLDING AS
LG & SP RÅDGIVNING AS
NOK 12.8m rev. · NOK 5.3m profit

LG & SP RÅDGIVNING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LG & SP RÅDGIVNING AS

Who owns LG & SP RÅDGIVNING AS?

FH KAPITAL HOLDING AS is the largest registered owner, with 51.0%.

What is the revenue of LG & SP RÅDGIVNING AS?

LG & SP RÅDGIVNING AS had revenue of NOK 12.8m in 2025.

Who is the general manager of LG & SP RÅDGIVNING AS?

Frode Andre Bull-Njaa Lefevre is registered as general manager of LG & SP RÅDGIVNING AS.

Where is LG & SP RÅDGIVNING AS based?

LG & SP RÅDGIVNING AS has its business address in Oslo.

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.