biztrac. BETA
COMPANY REGISTER PROFILE
984058624 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of other equipment

MOLAND OG SUNDBY AS

Org. no. 984058624 Limited company (AS) Larvik Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 90,000
Equity NOK 1.2m
Incorporated 2001
Share capital NOK 100,000

MOLAND OG SUNDBY AS is registered as a limited company in Larvik, Vestfold with organisation number 984058624. The business is classified under repair and maintenance of other equipment (NACE 33.190). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Mekanisk verksted samt hva hermed står i forbindelse, herunder også deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 90,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
▼ −8 %
Operating profit
NOK 90,000
▼ −74 %
Equity
NOK 1.2m
▼ −3 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
2.14
Very good
Current assets ÷ current liabilities
Profitability
4.4%
Weak
Return on total assets
Solidity
57.7%
Very good
Equity as a share of total capital

Who owns MOLAND OG SUNDBY AS?

MOLAND OG SUNDBY AS
NOK 3.8m rev. · NOK 90,000 profit

MOLAND OG SUNDBY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOLAND OG SUNDBY AS

Who owns MOLAND OG SUNDBY AS?

RB INDUSTRITJENESTER AS is the largest registered owner, with 50.0%.

What is the revenue of MOLAND OG SUNDBY AS?

MOLAND OG SUNDBY AS had revenue of NOK 3.8m in 2025.

Who is the general manager of MOLAND OG SUNDBY AS?

Kåre Sundby is registered as general manager of MOLAND OG SUNDBY AS.

Where is MOLAND OG SUNDBY AS based?

MOLAND OG SUNDBY AS has its business address in Larvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.