BIZTRAC BETA
Sports and recreation education

FOOTBALL CONSULTING NORWAY AS

Org. no. 922944512 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 30,000
Operating profit NOK 12,000
Equity NOK −22,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−22k kr).

FOOTBALL CONSULTING NORWAY AS is registered as a limited company in Lillestrøm, Akershus with organisation number 922944512. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester innenfor fotball.”. The most recent filed accounts, for the 2024 financial year, show NOK 30,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2024

Revenue
NOK 30,000
Operating profit
NOK 12,000
Equity
NOK −22,000
Est. value
NOK 64,000

Financial health · 2024

Liquidity
3.84
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-58.2%
Weak
Equity as a share of total capital

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

Who owns FOOTBALL CONSULTING NORWAY AS?

SONDRE SJØGREN JAKOBSEN
FOOTBALL CONSULTING NORWAY AS
NOK 30,000 rev. · NOK 12,000 profit

FOOTBALL CONSULTING NORWAY AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOOTBALL CONSULTING NORWAY AS

Who owns FOOTBALL CONSULTING NORWAY AS?

SONDRE SJØGREN JAKOBSEN is the largest registered owner, with 25.0%.

What is the revenue of FOOTBALL CONSULTING NORWAY AS?

FOOTBALL CONSULTING NORWAY AS had revenue of NOK 30,000 in 2024.

Where is FOOTBALL CONSULTING NORWAY AS based?

FOOTBALL CONSULTING NORWAY AS has its business address in Skedsmokorset.

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.