BIZTRAC BETA
Activities of advertising agencies

MEG&LIEN AS

Org. no. 921758413 Limited company (AS) Holmestrand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −871
Equity NOK 382,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

MEG&LIEN AS is registered as a limited company in Holmestrand, Vestfold with organisation number 921758413. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester, salg og kjøp av reklametjenester og annen forretningsmessig tjenesteyting, herunder også netthandel av bredt vareutvalg. Selskapet kan og ha deltakelse i andre selskaper herved i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −871 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −871
Equity
NOK 382,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns MEG&LIEN AS?

KJERSTI LIEN KLEVAN
MEG&LIEN AS
NOK 1.4m rev. · NOK −871 profit

MEG&LIEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEG&LIEN AS

Who owns MEG&LIEN AS?

KJERSTI LIEN KLEVAN is the largest registered owner, with 100.0%.

What is the revenue of MEG&LIEN AS?

MEG&LIEN AS had revenue of NOK 1.4m in 2025.

Who is the general manager of MEG&LIEN AS?

Kjersti Lien Klevan is registered as general manager of MEG&LIEN AS.

Where is MEG&LIEN AS based?

MEG&LIEN AS has its business address in Holmestrand.

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.