BIZTRAC BETA
Motion picture, video and television programme production activities

LUBERTH AS

Org. no. 934361385 Limited company (AS) Sandefjord Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 275,000
Operating profit NOK 24,000
Equity NOK 76,000
Incorporated 2024
Share capital NOK 30,000

LUBERTH AS is registered as a limited company in Sandefjord, Vestfold with organisation number 934361385. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen produksjon av video - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 275,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 275,000
Operating profit
NOK 24,000
Equity
NOK 76,000
Est. value
NOK 190,000

Financial health · 2025

Liquidity
4.68
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
78.7%
Weak
Equity as a share of total capital

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

Who owns LUBERTH AS?

NATHANIEL LUBERTH
LUBERTH AS
NOK 275,000 rev. · NOK 24,000 profit

LUBERTH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUBERTH AS

Who owns LUBERTH AS?

NATHANIEL LUBERTH is the largest registered owner, with 100.0%.

What is the revenue of LUBERTH AS?

LUBERTH AS had revenue of NOK 275,000 in 2025.

Who is the general manager of LUBERTH AS?

Nathaniel Luberth is registered as general manager of LUBERTH AS.

Where is LUBERTH AS based?

LUBERTH AS has its business address in Sandefjord.

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.