BIZTRAC BETA
Plumbing installation

69 GRADER RØR AS

Org. no. 931689533 Limited company (AS) Kåfjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK −34,000
Equity NOK 151,000
Incorporated 2023
Employees 8
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−34k kr).

69 GRADER RØR AS is registered as a limited company in Kåfjord, Troms with organisation number 931689533. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Installasjon og drift av varmeløsninger, ventilasjon, inneklima, miljø-og sanitæranlegg i bygninger og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK −34,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK −34,000
Equity
NOK 151,000
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
0.92
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.6%
Satisfactory
Equity as a share of total capital

Who owns 69 GRADER RØR AS?

LASSE ANDRE BJØRN
69 GRADER RØR AS
NOK 5.7m rev. · NOK −34,000 profit

69 GRADER RØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about 69 GRADER RØR AS

Who owns 69 GRADER RØR AS?

LASSE ANDRE BJØRN is the largest registered owner, with 50.0%.

What is the revenue of 69 GRADER RØR AS?

69 GRADER RØR AS had revenue of NOK 5.7m in 2024.

Who is the general manager of 69 GRADER RØR AS?

Lasse Andre Bjørn is registered as general manager of 69 GRADER RØR AS.

Where is 69 GRADER RØR AS based?

69 GRADER RØR AS has its business address in Olderdalen.

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.