biztrac. BETA
COMPANY REGISTER PROFILE
930014842 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Graphic design and visual communication activities

LILLE EYOLF AS

Org. no. 930014842 Limited company (AS) Oslo Incorporated 2022 Active
Operating profit NOK −25,000
Equity NOK 60,000
Incorporated 2022
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

LILLE EYOLF AS is registered as a limited company in Oslo, Oslo with organisation number 930014842. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper og andre tjenester som naturlig hører sammen med dette, herunder kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK −25,000
▼ −11 %
Equity
NOK 60,000
▼ −97 %
Est. value
NOK 53.5m

Financial health · 2025

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

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

Who owns LILLE EYOLF AS?

LILLE EYOLF AS
· NOK −25,000 profit

LILLE EYOLF AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LILLE EYOLF AS own?

LILLE EYOLF AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LILLE EYOLF AS

Who owns LILLE EYOLF AS?

FULL COURT AS is the largest registered owner, with 50.0%.

Who is the general manager of LILLE EYOLF AS?

Christian Bielke Steffensen is registered as general manager of LILLE EYOLF AS.

Where is LILLE EYOLF AS based?

LILLE EYOLF 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.