biztrac. BETA
COMPANY REGISTER PROFILE
914223121 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Manufacture of furniture

LØD AS

Org. no. 914223121 Limited company (AS) Kragerø Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 9.3m
Operating profit NOK −445,000
Equity NOK 739,000
Incorporated 2014
Employees 9
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−445k kr).

LØD AS is registered as a limited company in Kragerø, Telemark with organisation number 914223121. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tømring, båtbygging, møbel- og innredningsarbeider, eksport/import av relevante produkter samt generelle tjenester innen den maritime sektor.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.3m in revenue and NOK −445,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.3m
▼ −0 %
Operating profit
NOK −445,000
▼ −278 %
Equity
NOK 739,000
▼ −32 %
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
-13.0%
Not satisfactory
Return on total assets
Solidity
19.6%
Good
Equity as a share of total capital

Who owns LØD AS?

LØD AS
NOK 9.3m rev. · NOK −445,000 profit

LØD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØD AS

Who owns LØD AS?

GLØD HOLDING KRAGERØ AS is the largest registered owner, with 51.0%.

What is the revenue of LØD AS?

LØD AS had revenue of NOK 9.3m in 2025.

Who is the general manager of LØD AS?

Jo Borkhus is registered as general manager of LØD AS.

Where is LØD AS based?

LØD AS has its business address in Kragerø.

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.