biztrac. BETA
COMPANY REGISTER PROFILE
813851032 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Site preparation

PAD38 AS

Org. no. 813851032 Limited company (AS) Bamble Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 552,000
Operating profit NOK 299,000
Equity NOK −573,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−573k kr).

PAD38 AS is registered as a limited company in Bamble, Telemark with organisation number 813851032. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Opparbeidelse av hus og hyttefelt inklusiv kommunalteknisk VA- anlegg, Sprengning av større veianlegg/steinbrudd.”. The most recent filed accounts, for the 2025 financial year, show NOK 552,000 in revenue and NOK 299,000 in operating profit.

Former names: SPRENGNING AS

Key figures · 2025

Revenue
NOK 552,000
▲ +202 %
Operating profit
NOK 299,000
▲ +189 %
Equity
NOK −573,000
▲ +27 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
14.6%
Good
Return on total assets
Solidity
-65.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PAD38 AS?

PAD38 AS
NOK 552,000 rev. · NOK 299,000 profit

PAD38 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAD38 AS

Who owns PAD38 AS?

Fred Lyngmyr is the largest registered owner, with 100.0%.

What is the revenue of PAD38 AS?

PAD38 AS had revenue of NOK 552,000 in 2025.

Who is the general manager of PAD38 AS?

Fred Lyngmyr is registered as general manager of PAD38 AS.

Where is PAD38 AS based?

PAD38 AS has its business address in Stathelle.

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.