BIZTRAC BETA
Freight transport by road

NITTEBERG AS

Org. no. 931309862 Limited company (AS) Ullensaker Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 30.4m
Operating profit NOK 634,000
Equity NOK 675,000
Incorporated 2023
Employees 14
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-16 Adresseendring registrert 2026-02-16.

NITTEBERG AS is registered as a limited company in Ullensaker, Akershus with organisation number 931309862. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2023 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Godstransport på vei, salg og utleievirksomhet av varer og tjenester, samt annen nærliggende virksomhet. Selskapet utfører oppdrag innen avfallstransport.”. The most recent filed accounts, for the 2024 financial year, show NOK 30.4m in revenue and NOK 634,000 in operating profit.

Key figures · 2024

Revenue
NOK 30.4m
Operating profit
NOK 634,000
Equity
NOK 675,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns NITTEBERG AS?

NITTEBERG GRUPPEN AS
NITTEBERG AS
NOK 30.4m rev. · NOK 634,000 profit

NITTEBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NITTEBERG AS

Who owns NITTEBERG AS?

NITTEBERG GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of NITTEBERG AS?

NITTEBERG AS had revenue of NOK 30.4m in 2024.

Who is the general manager of NITTEBERG AS?

Jarle Andreas Nitteberg is registered as general manager of NITTEBERG AS.

Where is NITTEBERG AS based?

NITTEBERG AS has its business address in Nordkisa.

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.