BIZTRAC BETA
Activities of advertising agencies

NORSK TJENESTEDESIGN AS

Org. no. 813995832 Limited company (AS) Frogn Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 121,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

NORSK TJENESTEDESIGN AS is registered as a limited company in Frogn, Akershus with organisation number 813995832. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning innen tjenestedesign samt delta i virksomhet med beslektet type aktivitet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 121,000
Est. value
NOK 94,000

Financial health · 2025

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

Who owns NORSK TJENESTEDESIGN AS?

SIMEN WILSHER LOHRE
NORSK TJENESTEDESIGN AS
NOK 0 rev. · NOK −2,000 profit

NORSK TJENESTEDESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK TJENESTEDESIGN AS

Who owns NORSK TJENESTEDESIGN AS?

SIMEN WILSHER LOHRE is the largest registered owner, with 100.0%.

What is the revenue of NORSK TJENESTEDESIGN AS?

NORSK TJENESTEDESIGN AS had revenue of NOK 0 in 2025.

Who is the general manager of NORSK TJENESTEDESIGN AS?

Simen Wilsher Lohre is registered as general manager of NORSK TJENESTEDESIGN AS.

Where is NORSK TJENESTEDESIGN AS based?

NORSK TJENESTEDESIGN AS has its business address in Drøbak.

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.