BIZTRAC BETA
Rental and leasing of cars and light motor vehicles

OTTO MOE BILUTLEIE AS

Org. no. 968024736 Limited company (AS) Namsos Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 768,000
Equity NOK 10.3m
Incorporated 1993
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OTTO MOE BILUTLEIE AS is registered as a limited company in Namsos, Trøndelag with organisation number 968024736. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handel og servicevirksomhet og det som dermed står i forbindelse, samt å delta i annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 768,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 768,000
Equity
NOK 10.3m
Est. value
NOK 7.5m

Financial health · 2024

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

Who owns OTTO MOE BILUTLEIE AS?

OTTO MOE HOLDING AS
OTTO MOE BILUTLEIE AS
NOK 3.0m rev. · NOK 768,000 profit

OTTO MOE BILUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OTTO MOE BILUTLEIE AS

Who owns OTTO MOE BILUTLEIE AS?

OTTO MOE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OTTO MOE BILUTLEIE AS?

OTTO MOE BILUTLEIE AS had revenue of NOK 3.0m in 2024.

Where is OTTO MOE BILUTLEIE AS based?

OTTO MOE BILUTLEIE AS has its business address in Namsos.

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.