BIZTRAC BETA
Activities of agents involved in the wholesale of other particular products

LEXOW AGENT AS

Org. no. 952159518 Limited company (AS) Ringerike Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK 15.1m
Incorporated 1989
Share capital NOK 1,000,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

LEXOW AGENT AS is registered as a limited company in Ringerike, Buskerud with organisation number 952159518. The business is classified under activities of agents involved in the wholesale of other particular products (NACE 46.180). The company was incorporated in 1989. Registered share capital is NOK 1,000,000, divided into 2800 shares. The company's stated purpose is: “Drive investeringsvirksomhet og hva derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 15.1m
Est. value
NOK 18.9m

Financial health · 2024

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

Who owns LEXOW AGENT AS?

AGNETHE KNUTSDATTER REYMERT
LEXOW AGENT AS
NOK 0 rev. · NOK −18,000 profit

LEXOW AGENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEXOW AGENT AS

Who owns LEXOW AGENT AS?

AGNETHE KNUTSDATTER REYMERT is the largest registered owner, with 100.0%.

What is the revenue of LEXOW AGENT AS?

LEXOW AGENT AS had revenue of NOK 0 in 2024.

Who is the general manager of LEXOW AGENT AS?

Agnethe Knutsdatter Reymert is registered as general manager of LEXOW AGENT AS.

Where is LEXOW AGENT AS based?

LEXOW AGENT AS has its business address in Hønefoss.

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.