BIZTRAC BETA
Joinery installation

BONI NO 1 AS

Org. no. 995113821 Limited company (AS) Stavanger Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 155,000
Operating profit NOK 21,000
Equity NOK −24,000
Incorporated 2010
Share capital NOK 100,000

Signals

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

BONI NO 1 AS is registered as a limited company in Stavanger, Rogaland with organisation number 995113821. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Snekkerarbeid, montering av dører, vinduer, kjøkken, bad, garasjer og terrasser, samt virksomhet som står i forbindelse med dette, herunder investering i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 155,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2025

Revenue
NOK 155,000
Operating profit
NOK 21,000
Equity
NOK −24,000
Est. value
NOK 107,000

Financial health · 2025

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-9.8%
Weak
Equity as a share of total capital

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

Who owns BONI NO 1 AS?

TROND LEIREN
BONI NO 1 AS
NOK 155,000 rev. · NOK 21,000 profit

BONI NO 1 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BONI NO 1 AS

Who owns BONI NO 1 AS?

TROND LEIREN is the largest registered owner, with 67.0%.

What is the revenue of BONI NO 1 AS?

BONI NO 1 AS had revenue of NOK 155,000 in 2025.

Who is the general manager of BONI NO 1 AS?

Trond Leiren is registered as general manager of BONI NO 1 AS.

Where is BONI NO 1 AS based?

BONI NO 1 AS has its business address in Stavanger.

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.