BIZTRAC BETA
Activities of advertising agencies

NETTLY AS

Org. no. 915212441 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 236,000
Equity NOK 1.1m
Incorporated 2015
Share capital NOK 40,000

Signals

1 flags
  • Nylig endring 2026-07-22 Adresseendring registrert 2026-07-22.

NETTLY AS is registered as a limited company in Oslo, Oslo with organisation number 915212441. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2015. Registered share capital is NOK 40,000, divided into 400 shares. The company's stated purpose is: “Levere tjenester innen digital markedsføring og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 236,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 236,000
Equity
NOK 1.1m
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
2.59
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
61.4%
Very good
Equity as a share of total capital

Who owns NETTLY AS?

THORSTEIN NORDBY
NETTLY AS
NOK 1.9m rev. · NOK 236,000 profit

NETTLY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NETTLY AS

Who owns NETTLY AS?

THORSTEIN NORDBY is the largest registered owner, with 100.0%.

What is the revenue of NETTLY AS?

NETTLY AS had revenue of NOK 1.9m in 2024.

Who is the general manager of NETTLY AS?

Thorstein Nordby is registered as general manager of NETTLY AS.

Where is NETTLY AS based?

NETTLY 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.