biztrac. BETA
COMPANY REGISTER PROFILE
928848795 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

NESODDEN HÅNDVERKTJENESTER AS

Org. no. 928848795 Limited company (AS) Nesodden Incorporated 2022 Active
Revenue 2025 NOK 1.2m
Operating profit NOK 14,000
Equity NOK 42,000
Incorporated 2022
Share capital NOK 30,000

NESODDEN HÅNDVERKTJENESTER AS is registered as a limited company in Nesodden, Akershus with organisation number 928848795. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Bygg og vedlikehold av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▲ +7 %
Operating profit
NOK 14,000
▼ −69 %
Equity
NOK 42,000
▼ −16 %
Est. value
NOK 67,000

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
3.2%
Weak
Return on total assets
Solidity
10.1%
Weak
Equity as a share of total capital

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

Who owns NESODDEN HÅNDVERKTJENESTER AS?

NESODDEN HÅNDVERKTJENESTER AS
NOK 1.2m rev. · NOK 14,000 profit

NESODDEN HÅNDVERKTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESODDEN HÅNDVERKTJENESTER AS

Who owns NESODDEN HÅNDVERKTJENESTER AS?

Frode Nilsen is the largest registered owner, with 100.0%.

What is the revenue of NESODDEN HÅNDVERKTJENESTER AS?

NESODDEN HÅNDVERKTJENESTER AS had revenue of NOK 1.2m in 2025.

Where is NESODDEN HÅNDVERKTJENESTER AS based?

NESODDEN HÅNDVERKTJENESTER AS has its business address in Nesoddtangen.

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.