BIZTRAC BETA
Activities of advertising agencies

LEEL MEDIA AS

Org. no. 934859898 Limited company (AS) Bodø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −30,000
Equity NOK 15,000
Incorporated 2025
Share capital NOK 50,000

Signals

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

LEEL MEDIA AS is registered as a limited company in Bodø, Nordland with organisation number 934859898. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Selge varer og tjenester innen markedsføring og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −30,000
Equity
NOK 15,000
Est. value
NOK 1.9m

Financial health · 2025

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

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

Who owns LEEL MEDIA AS?

LEEL AS
LEEL MEDIA AS
NOK 1.8m rev. · NOK −30,000 profit

LEEL MEDIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEEL MEDIA AS

Who owns LEEL MEDIA AS?

LEEL AS is the largest registered owner, with 100.0%.

What is the revenue of LEEL MEDIA AS?

LEEL MEDIA AS had revenue of NOK 1.8m in 2025.

Who is the general manager of LEEL MEDIA AS?

Benjamin André Kristiansen is registered as general manager of LEEL MEDIA AS.

Where is LEEL MEDIA AS based?

LEEL MEDIA AS has its business address in Tverlandet.

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.