BIZTRAC BETA
Retail sale of pleasure boats and equipment

BYGGPLAST BÅTUTSTYR AS

Org. no. 965317392 Limited company (AS) Fredrikstad Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 15.2m
Operating profit NOK 2.0m
Equity NOK 7.0m
Incorporated 1992
Employees 12
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.

BYGGPLAST BÅTUTSTYR AS is registered as a limited company in Fredrikstad, Østfold with organisation number 965317392. The business is classified under retail sale of pleasure boats and equipment (NACE 47.632). The company was incorporated in 1992 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Handelsvirksomhet og annet som måtte stå i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.2m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 15.2m
Operating profit
NOK 2.0m
Equity
NOK 7.0m
Est. value
NOK 10.7m

Financial health · 2025

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

Who owns BYGGPLAST BÅTUTSTYR AS?

NORWAY MARINE SUPPLY AS
BYGGPLAST BÅTUTSTYR AS
NOK 15.2m rev. · NOK 2.0m profit

BYGGPLAST BÅTUTSTYR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGGPLAST BÅTUTSTYR AS

Who owns BYGGPLAST BÅTUTSTYR AS?

NORWAY MARINE SUPPLY AS is the largest registered owner, with 95.0%.

What is the revenue of BYGGPLAST BÅTUTSTYR AS?

BYGGPLAST BÅTUTSTYR AS had revenue of NOK 15.2m in 2025.

Where is BYGGPLAST BÅTUTSTYR AS based?

BYGGPLAST BÅTUTSTYR AS has its business address in Fredrikstad.

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.